ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Philip,

Wow! That worked! Why did that fix the problem?

What happened is that when I added ICEFaces capabilities to my project, the wizard in MyEclipse said that ICEFaces needed to run in JSF 1.1 compatibility mode. At that point it told me it need to modify web.xml and faces-config.xml for that purpose and asked me if I wanted to proceed, so I said yes.

I would be more than happy to close the issue I opened. I looked around for a way to close, but I could not figure it out. How exactly do I close the issue?

Thanks so much for you help!
Ryan

philip.breau wrote:

Change your web.xml version to 2.5 and please close the jira.

Philip,

I packaged my EAR according to your diagram, but injection still failed.

I opened an issue since this does not "seem" to be a configuration nor programmatic error on my part:

http://jira.icefaces.org//browse/ICE-3360

There you can download 2 zip files. They contain the EAR files and all of the respective project files. Injection works for the zip called JSF Only, and fails for the JSF ICEFaces zip. The URL required for the test is in the comments.

ICEFaces components still work, it just seems that something is causing injection to get blocked. I turned on JSF and EJB logging to FINEST, and still no suspicious error messages turned up.

Any light you can shed on this would be greatly appreciated.

Thanks,
Kurzweil4

Philip,

Thanks for the response.

Are you manually packing your EAR to get it set up like that?

If I understand correctly, all of the jars in the WAR should be in the top level of the EAR. What I am confused about is the my-services.jar. Are you saying that my managed mean (which is what I am injecting into) should be in its own jar?

Thanks,
Kurzweil4

philip.breau wrote:

Here's a layout that works for me on Glassfish with ICEfaces and Facelets, using Toplink:

Code:

/ear
    /META-INF
       application.xml
    my-ejb.jar
    backport-util-concurrent.jar
    commons-beanutils.jar
    commons-collections.jar
    commons-digester.jar
    commons-discovery.jar
    commons-el.jar
    commons-fileupload.jar
    commons-logging.jar
    el-ri.jar
    icefaces-comps.jar
    icefaces-facelets.jar
    icefaces.jar
    my-war.war
        /WEB-INF/
             lib/my-services.jar
                    @EJB injection

If this layout doesn't work for you, perhaps you could post your example.

Philip

Why don't you use Stateful EJBs? Then at the end of your wizard, your submit button would call an action method in your backng bean that would call a method in the Stateful EJB annotated with @Remove, which will cause it to be removed from memory when the call is finished. If they never finish the process, the EJB will eventually time out and be removed from memory.

I believe in JSF 2.0 that there will be the ability to use the EJB directly as the backing bean instead of using a JSF managed bean as a proxy.

Kurzweil4

CWSmith wrote:

That doesn't seem like a very viable option. If I have a wizard for example, or a single application that submits forms and goes from one page to another, if I redirect I lose any request scoped beans.

So if my form submits, and I want the next page to display a message to the user based on what happened during that submission, on the way to the next page the request scoped bean is lost.

Some might say to use all session scoped beans, but that doesn't seem like a very good fix either... then you are sitting around with x more beans in memory per user and that is just unnecessary.

I am using MyEclipse 6.0.1, ICEFaces 1.7.1, and Sun Application Server 9.1 (Glassfish v2).

I have a simple EAR with an EJB-Jar with one session bean, and a WAR with one page and one managed session bean that uses injection to get an instance of the session EJB.

When I add ICEFaces capabilities to my web project, and deploy the EAR, EJB injection stops working. There are no error messages in the server's log related to this, it just simply stops injecting.

Here are the following configurations I have tried and the results:

JSF Capabilities Only: Injection Works
JSF and Facelets Capabilities: Injection Works
JSF and ICEFaces Capabilities (no Facelets): Injection Fails
JSF and ICEFaces and ICEFaces Facelets Capabilities: Injection Fails

Any ideas on this? I can find nothing on the web about EJB injection problems when using ICEFaces.

Thanks,
Kurzweil4

mark.collette wrote:

That mode only affects minute details of view creation. Everything in JSF 1.2 works.

Thanks!!

I want to run ICEFaces 1.7.1, and the docs say that it must run with JSF in 1.1 combatibility mode. When this happens, do any JSF 1.2 features become unavailable? If so, which ones?

Also, why does it have to run in this mode?

Thanks,
Kurzweil4

I was wondering if anyone has tried using JSecurity with ICEFaces, and how well or badly this went. Are there any compatibility issues?

Thanks,
Kurzweil4

Does ICEFaces guard against refresh and back buttons or do you have to implement your own solution?

Thanks,
Kurzweil4

Cyrill,

Sounds like your knowledge on this matter is greater than mine :-)

Kurzweil4

This may be a little off topic, but I am having a lot of trouble finding an affordable web host where I can run a JEE5 application with EJB 3.0.

Anyone have any sites to suggest?

Thanks,
Kurzweil4

I discovered the problem. My Model project was using a JAR File deployment descriptor instead of an EJB Jar File deployment descriptor. Once I fixed this, it was smooth sailing.

The thing that really had me confused was the fact that it still worked in the embedded OC4J.

Kurzweil4

Frank,

I got it to work finally in the embedded OC4J server by removing the <distributable> tag from the web.xml.

When deployed though, it cannot resolve my EL expression DepartmentBean.departments. At this point I no longer beleive this to be related to ICEfaces. I think this is either related to my deployment descriptors or something being missing from the provided web.xml.

If you are still interested in helping I can send the files to you.

Thanks,
Kurzweil4

frank.ye wrote:

Without your web project and details, it is hard to guess...

But could you use the stand alone server comes with JDeveloper rather than the embedded one.

You could use the steps as follows:

http://www.oracle.com/technology/obe/obe1013jdev/deployment/deployment.htm

If it is still not working for you, please send a simple web project ...

Frank,

Thanks for your response. The link you gave is actually the document I was following for deployment. When I get home today, I will send you the simple project I am using in JDeveloper.

Kurzweil4

This is related to my previous post:

http://www.icefaces.org/JForum/posts/list/5205.page

Using the web.xml file from http://support.icesoft.com/jive/entry.jspa?entryID=752&categoryID=80 ...deployment from Eclipse to JBoss and OC4J work and without any configuration needed to the OC4J server.

When deploying from JDeveloper on the other hand ...both of these do not work. When using the default web.xml, I cannot change tabs as before, but both JBoss and OC4J give the same error message. When using the specially configured web.xml from above, both of them fail.

Looking into the application log on the standalone OAS, it says that it is failing because 'departments' cannot be found in the Departments entity bean when resolving the EL expression DepartmentsBean.departments for my data table. Previously when I was using the data table with the default web.xml and the data table was not in a tab, I did not get this error. The data displayed as expected.

Currently, even though the project in Eclipse does not have any database connection defined, it does not error when I switch to the tab where the data table is located. It just displays the headers. I need to test what happens when I have an Entity bean defined in the project.

Any ideas on these issues?

Thanks,
Kurzweil4