> Replace JSF with an up to date version. JSF lives in server/default/ > deploy/jboss-web.deployer/jsf-libs/{jsf-api.jar, jsf-impl.jar}. Thanks, I'll get that into our FQA. Isn't the "two listeners installed" just a warning? Seam still works as far as I know. I see this same message when deploying to Tomcat.

> Or use JBoss 5. Which won't work with hotdeployment - another thread ;) This is a major issue atm. From my tests I can't even get it to see new Facelets templates. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

On Tue, Apr 7, 2009 at 1:30 PM, Max Rydahl Andersen <manderse(a)redhat.com&gt;wrote: > > ----- "Dan Allen" <dan.j.allen(a)gmail.com&gt; wrote: > > > > Replace JSF with an up to date version. JSF lives in server/default/ > > > deploy/jboss-web.deployer/jsf-libs/{jsf-api.jar, jsf-impl.jar}. > > > > Thanks, I'll get that into our FQA. > > > > Isn't the "two listeners installed" just a warning? Seam still works > > as far as I know. I see this same message when deploying to Tomcat. > > > > Error Message: > 23:56:56,423 ERROR [SeamPhaseListener] uncaught exception > java.lang.IllegalStateException: No phase id bound to current thread (make > sure you do not have two SeamPhaseListener instances installed) > at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:162) > at > org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:174) > at > org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext.java:90) > at org.jboss.seam.contexts.PageContext.remove(PageContext.java:104) > > Looks like an exception to me ;) Hmm, so when the app starts it probably lists a warning too. I actually haven't deployed to 4.2.3.GA yet. I wonder if I deployed an app if I would see this or if there is something specific about the user's app.

It only happens for special people.... Before it were for projects with a capital letter - I haven't identified the trigger yet for this round. /max *From:* Dan Allen <mailto:dan.j.allen@gmail.com> *Sent:* Tuesday, April 07, 2009 8:32 PM *To:* Max Rydahl Andersen <mailto:manderse@redhat.com> *Cc:* Pete Muir <mailto:pmuir@redhat.com> ; seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> *Subject:* Re: [seam-dev] java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)) On Tue, Apr 7, 2009 at 1:37 PM, Dan Allen <dan.j.allen(a)gmail.com <mailto:dan.j.allen@gmail.com>> wrote: On Tue, Apr 7, 2009 at 1:30 PM, Max Rydahl Andersen <manderse(a)redhat.com <mailto:manderse@redhat.com>> wrote: ----- "Dan Allen" <dan.j.allen(a)gmail.com <mailto:dan.j.allen@gmail.com>> wrote: > > Replace JSF with an up to date version. JSF lives in server/default/ > > deploy/jboss-web.deployer/jsf-libs/{jsf-api.jar, jsf-impl.jar}. > > Thanks, I'll get that into our FQA. > > Isn't the "two listeners installed" just a warning? Seam still works > as far as I know. I see this same message when deploying to Tomcat. > Error Message: 23:56:56,423 ERROR [SeamPhaseListener] uncaught exception java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed) at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:162) at org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:174) at org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext.java:90) at org.jboss.seam.contexts.PageContext.remove(PageContext.java:104) Looks like an exception to me ;) Hmm, so when the app starts it probably lists a warning too. I actually haven't deployed to 4.2.3.GA <http://4.2.3.GA> yet. I wonder if I deployed an app if I would see this or if there is something specific about the user's app. I can't reproduce. I wonder what else I need to do to replicate the user's situation. Created EAR w/ JBoss Tools 3.0.0.CR2. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. ------------------------------------------------------------------------ _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

A workaround is removing jboss-seam.jar from WEB-INF/lib If jboss-seam.jar isn't in WEB-INF/lib, where is it?

-Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

On Wed, Apr 8, 2009 at 5:42 PM, Snjezana Peco <snjezana.peco(a)redhat.com <mailto:snjezana.peco@redhat.com>> wrote: Dan Allen wrote: A workaround is removing jboss-seam.jar from WEB-INF/lib If jboss-seam.jar isn't in WEB-INF/lib, where is it? It is always in the EAR project. Okay, so why would you want it in the WAR too?

-Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

I don't want it in the WAR. However, if it is added in any way to the WEB-INF/lib directory of the WAR project, you will face the issue described in this thread (unless you are using JBoss AS 4.2.2). With the way Seam is designed, if you have Seam on the classpath twice, the results are undefined. In some cases it will work, others it will not. The reason for the initial warning is that Seam bundles faces-config.xml and JSF is going to find it twice and try to start the phase listener twice. Hmm...

-Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

> Dan, as discussed before this is a broken design - duplicates on a > classpath is not illegal; only the first one should be listened to > AFAIK. > > Snjezana, if you remove the seam.jar from web-inf/lib does the > compilation still work ? Or is it WTP that is putting it in there for > us ? The compilation always works. WTP is not putting this file in there. It is possible that earlier versions of JBoss Tools (before releasing JBoss AS 4.2.3) were copying the file to WEB-INF/lib.

Snjeza > /max >> -Dan >> >> -- >> Dan Allen >> Senior Software Engineer, Red Hat | Author of Seam in Action >> >> http://mojavelinux.com >> http://mojavelinux.com/seaminaction >> http://in.relation.to/Bloggers/Dan >> >> NOTE: While I make a strong effort to keep up with my email on a daily >> basis, personal or other work matters can sometimes keep me away >> from my email. If you contact me, but don't hear back for more than >> a week, >> it is very likely that I am excessively backlogged or the message was >> caught in the spam filters. Please don't hesitate to resend a >> message if >> you feel that it did not reach my attention.

Guys, You should only have one jboss-seam.jar per application. Period. Please stop trying to invent new packaging schemes ;-) Knowing Max, the next question is "Why?". Yes, the WAR classloader will hide the EAR classloader, however you end up with two problems: * if you try to load a component on the WAR classloader, then use it in the EJB jar, you will get a CCE (this is a bonus problem to the one you found) * classloaders don't just load classes, they also posses the ability to load resources, and also (critically) the ability to load all the resources in every classpath root on the classpath. So, if you add jboss-seam.jar twice, all the resources inside will be on the classpath twice. And, in fact, this behaviour is logical, and correct if you think it through. So, please fix this in JBT :-) On 9 Apr 2009, at 11:50, Max Rydahl Andersen wrote: > >>> Dan, as discussed before this is a broken design - duplicates on >>> a classpath is not illegal; only the first one should be listened >>> to AFAIK. >>> >>> Snjezana, if you remove the seam.jar from web-inf/lib does the >>> compilation still work ? Or is it WTP that is putting it in there >>> for us ? >> >> The compilation always works. >> WTP is not putting this file in there. It is possible that earlier >> versions of JBoss Tools (before releasing JBoss AS 4.2.3) were >> copying the file to WEB-INF/lib. > I don't think JBoss tools changed behavior in this aspect. The > question is if JBT EAR projects actually put the seam jar both in > ear and in web-inf/lib in the projects (not the deploy). > That should not have any sideeffects (but it does because of the > way seam 2.1.x is doing things), but if that is the case then we > can fix it by not having the web-inf/lib/seam.jar. > > /max >> >> Snjeza >>> /max >>>> -Dan >>>> >>>> -- >>>> Dan Allen >>>> Senior Software Engineer, Red Hat | Author of Seam in Action >>>> >>>> http://mojavelinux.com >>>> http://mojavelinux.com/seaminaction >>>> http://in.relation.to/Bloggers/Dan >>>> >>>> NOTE: While I make a strong effort to keep up with my email on a >>>> daily >>>> basis, personal or other work matters can sometimes keep me away >>>> from my email. If you contact me, but don't hear back for more >>>> than a week, >>>> it is very likely that I am excessively backlogged or the >>>> message was >>>> caught in the spam filters. Please don't hesitate to resend a >>>> message if >>>> you feel that it did not reach my attention. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Max Rydahl Andersen wrote: >>> Dan, as discussed before this is a broken design - duplicates on >>> a classpath is not illegal; only the first one should be listened >>> to AFAIK. >>> >>> Snjezana, if you remove the seam.jar from web-inf/lib does the >>> compilation still work ? Or is it WTP that is putting it in there >>> for us ? >> >> The compilation always works. >> WTP is not putting this file in there. It is possible that earlier >> versions of JBoss Tools (before releasing JBoss AS 4.2.3) were >> copying the file to WEB-INF/lib. > I don't think JBoss tools changed behavior in this aspect. The > question is if JBT EAR projects actually put the seam jar both in > ear and in web-inf/lib in the projects (not the deploy). > That should not have any sideeffects (but it does because of the > way seam 2.1.x is doing things), but if that is the case then we > can fix it by not having the web-inf/lib/seam.jar. I see now that I worded this wrongly. What I meant was: If JBT packaging ends up with the deployment having 2 physical seperate seam.jar jar's then that is wrong. If JBT packaging ends up with the deployment having 1 physical jar, referenced from MANIFEST.MF and application.ml then I can't fix that - and would like to know why that is causing a failure (since it shouldn't imo)

/max > > /max >> Snjeza >>> /max >>>> -Dan >>>> >>>> -- >>>> Dan Allen >>>> Senior Software Engineer, Red Hat | Author of Seam in Action >>>> >>>> http://mojavelinux.com >>>> http://mojavelinux.com/seaminaction >>>> http://in.relation.to/Bloggers/Dan >>>> >>>> NOTE: While I make a strong effort to keep up with my email on a >>>> daily >>>> basis, personal or other work matters can sometimes keep me away >>>> from my email. If you contact me, but don't hear back for more >>>> than a week, >>>> it is very likely that I am excessively backlogged or the >>>> message was >>>> caught in the spam filters. Please don't hesitate to resend a >>>> message if >>>> you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev