[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Bruce Link updated JBIDE-4166: ------------------------------ Attachment: infosys-ear.zip infosys-ds.xml Zipped files from C:\apps\workspace3.4.2\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_4.2_Server\deploy directory datasource file from above directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4166: -------------------------------------- The problem is the way in which the classloader within JBoss AS 4.2.3 works. This problem doesn't exist in JBoss AS 4.2.2 and JBoss AS 5.0.1. You can try the following workaround: - remove jboss-seam.jar from Java EE Module Dependencies within the EJB project - add jboss-seam.jar from the EAR project to the classpath of the EJB project as shown in the screencast http://screencast.com/t/91Ro9ngFGZM -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4166. -------------------------------- Resolution: Done Workaround is described... issue is in underlying runtime. Resolving. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] luc mercier commented on JBIDE-4166: ------------------------------------ I confirm that the issue exists with JBoss EAP 4.3.0.GA_CP03 as well. This is rather annoying, because it is the version that is bundled into JBoss Developer Studio 2.0.0.GA. What I observed: using JBoss DS 2.0.0.GA, jdk 1.6, and using everything as they come in DS 2.0.0. * Created a first seam web project with the wizard, called "seam2Test", deployment EAR, using Seam 2.0 -> it worked * Creates another seam web project with the wizard, exact same settings, called "b" -> I got the "java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)" error. I then installed JBoss AS 4.2.2 on the side, configured DS to use it, and it worked. Incompatibilities between version are hard to avoid once in a while. But it is very disappointing that they also occur while using a pre-bundled product. What is the $99 for, if not to avoid incompatibilities? I didn't find a JBoss DS Jira issue on this; should there be one? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4166: --------------------------------------- Fix Version/s: 3.0.1.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4166: --------------------------------------- Assignee: Scott M Stark (was: Snjezana Peco) Scott, i'm at the end of reasoning around this issue apparently caused by changes in the classloader in AS 4.2.2 to AS 4.2.3. Any idea why we get a different behavior in the same code scanning of classpaths when: - Using different letters in deployment name (fseam works different than seam even though the content of the EAR is exactly the same beyond the name) - Zipped ear works, unzipped ear does not - Same seam.jar works on AS 4.2.2 but not on AS 4.2.3 (same for corresponding EAP's) Any ideas ? If you have time to look there is an attached ear on this issue, no installation of JBoss Tools/JBDS required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-4166: --------------------------------------- I've tested Snjezana's patch. I don't see any problems. It seems to work. Max, shoud we commit it to svn? At least to trunk to test it more carefully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-4166: --------------------------------------- EAR/lib works in Eclipse 3.5 M6. I've tested it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4166: -------------------------------------------- just to be sure - this just affects Seam 2.x projects, right ? Seam 1.2.x is as before ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4166: -------------------------------------------- Here is the explanation of why it is occurring: This issue (the WARN message that SeamPhaseListener spits out and ultimately the application isn't accessible), has come up frequently in user forums but has ended up without any clean solutions. I just tried out the application attached to the JBIDE-4166 JIRA and here's what causes this issue: Exploded deployment: -------------------- 4.2.2 - The deployment framework: -------------------- 1) During deploy, it picks up the EAR/xxx-ejb.jar. Looks at its Manifest.mf and finds jboss-seam listed. So creates a tmp out of this and puts it in the tmp folder and adds it to classpath of the app. Let's call this temped file as tmpAjboss-seam.jar. 2) Later on during deploy, it picks up EAR/jboss-seam.jar (since its listed as a module in application.xml) and creates a temp jar out of this and adds to classpath of the app. Let's call this temped file as tmpBjboss-seam.jar. 3) Ultimately, we now have 2 (duplicated) temp versions of the same jboss-seam jar file. 4) Later on during the servlet context initialization of the seam application, the com.sun.faces.config.ConfigListener.contextInitialized (from jsf-impl.jar available in the AS) gets all META-INF/faces-config.xml resources in the application's classpath. This URL list now contains tmpAjboss-seam.jar and tmpBjboss-seam.jar (the duplicated temp versions of jboss-seam.jar). 5) Then the xmls corresponding to these URLs are parsed corresponding LifecycleBean(s) are created out of these. 6) The phase listeners (ex: SeamPhaseListener) are then added to a list maintained in com.sun.faces.config.beans.LifecycleBean. However, before adding the LifecycleBean does a check for phase listeners already registered with the given name. If present, then it *ignores* the next phase listener with the same name: public void addPhaseListener(String phaseListener) { if (!(this.phaseListeners.contains(phaseListener))) { ...// some logic this.phaseListeners.add(phaseListener); } } Ultimately, each of these phaseListeners are instantiated and invoked. Because of this logic involved in the LifecycleBean, the SeamPhaseListener is registered only once, even though 2 (duplicate temp) jars with faces-config.xml contained this listener. In 4.2.3 - The jsf-impl.jar version is different and the classes have been refactored. But the logic involved is the same till step#4 above. In the later steps, the call goes to com.sun.faces.config.processor.LifecycleProcessor. Here there is no check for existing phaseListeners with the same name. As a result, the SeamPhaseListener is instantiated twice which leads to it complaining: 15:40:49,386 WARN [SeamPhaseListener] There should only be one Seam phase listener per application Ultimately this leads to an exception while accessing the application (which i believe is related to the incorrect phase listener coming into picture). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4166: --------------------------------------- Fix Version/s: 3.0.2.GA (was: 3.0.1.GA) Keeping it open until we find the true fix for it, but moving it to 3.0.2 since 3.0.1 got a workaround AND fix for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4166: --------------------------------------- Assignee: (was: Scott M Stark) Unassign for now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4166: --------------------------------------- Assignee: Alexey Kazakov Priority: Major (was: Critical) The explanation from Jiri shows how to create a project that will always work when we dependent on Eclipse 3.4 not supporting EAR 5 libs correctly. If we could adjust Seam wizard creation to do this then we would solving alot of EAP 4.x users problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Snjezana Peco reassigned JBIDE-4166: ------------------------------------ Assignee: Snjezana Peco (was: Alexey Kazakov) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Anton Klimkovich closed JBIDE-4166. ----------------------------------- Verified on 2.1.0.GA-N200907270215-H117 and JBossTools-Update-3.1.0.M3-N200907241200-H100 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira