EJB Injection Stops Working After Adding ICEFaces Capabil.

I cannot do that in this case because I am deploying to a server which was not started from MyEclipse. I was unable to get the Sun 9.1 app server to launch from MyEclipse 6.0.1.

Anyway, I did not find any errors in the server’s log file. Wouldn’t these same errors show up there?

Thanks,
Kurzweil4

@support-nipun wrote:

Can you go to <workspace>/.metadata/.log file and check what error gets logged there.

In this case I think it is either something about ICEFaces’ run-time functionality or a configuration issue. If I undeploy the app, then deploy the EAR without ICEFaces, injection works without restarting the server.

@support-rkalla wrote:

Kurzweil4,
There is something going on the depths of the server’s classloader if what you are describing is happening… you can *Try* and deploy to a stopped app server, and then remove the facelets JARs, and then fire up the app server and see if suddenly injection works.

Also you might be able to login to the admin console and check the server logs, see if Glassfish is writing out anything helpful (maybe a class version mismatch or something like that?) to the log.

I really don’t have any great suggestions here, I’ve actually seen certain web framework JAR combinations (just installed by hand) segfault a server on a startup.

Yeah. I checked and I could not find anything there. I made a post also, but I got no replies.

I opened a bug issue, but since I am not a paying customer with them, I don’t know how soon it will get assigned to someone. The link is here if you want to vote on it:

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

You may also be able to download the two zip files I uploaded which contain the project folders and EAR files. One which is JSF only and works, and one which is JSF + ICEFaces and does not work. I explain how the test works in the comments.

I have tried to find any kind of configuration settings I could think of that might prevent injection from happening, but so far I have turned up empty handed.

Since there are no error messages in Glassfish’s server log, the only other thing I can think of is to try to find a way to turn on some kind of debug level logging there.

At this point I am dead in the water. I can do nothing until ICESoft does something with my issue.

I tried deploying to Geronimo to see if it is only Glassfish, but for the life of me I could not figure out how to deploy with a server-side datasource set up. Whatever JNDI name I use in persistence.xml it doesn’t like, and fails to deploy.

@support-rkalla wrote:

God that’s a weird one… have you checked the ICEfaces forums to see if other folks are reporting this? You can’t be the first to notice this… injection missing is a pretty big thing.