[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4166) Seam Web EAR project using Seam 2.1.1.GA does not work on JBoss AS 4.2.3
[
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.
Seam Web EAR project using Seam 2.1.1.GA does not work on JBoss AS
4.2.3
------------------------------------------------------------------------
Key: JBIDE-4166
URL: https://jira.jboss.org/jira/browse/JBIDE-4166
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows XP, JBoss AS 4.2.3, Seam 2.1.1.GA, Eclipse 3.4.2, JBoss
Tools 3.0.0.GA plus nightly 3.0.1 updates
Reporter: Bruce Link
Assignee: Scott M Stark
Fix For: 3.0.1.GA
Attachments: infosys-ds.xml, infosys-ear.ear, infosys-ear.zip
Created new seam web project using mysql connection (File>new>Seam Web Project)
Select EAR project with seam 2.1.1.GA
Ran project on JBoss 4.2.3 from JBoss Tools
Get warning:
13:40:57,481 WARN [MainDeployer] Found non-jar deployer for jboss-seam.jar:
MBeanProxyExt[jboss.ejb3:service=EJB3Deployer]
13:40:57,919 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ignoring config=LoaderRepositoryConfig(repositoryName:
seam.jboss.org:loader=infosys, repositoryClassName:
org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName:
org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig:
java2ParentDelegation=false)
Project failed to run
:13:41:21,513 WARN [SeamPhaseListener] uncaught exception, passing to exception handler
java.lang.IllegalStateException: No phase id bound to current thread (make sure you do
not have two SeamPhaseListener instances installed)
Traceback similar to post in JBoss Forum
Exporting ear file works (when ear file copied manually to deploy folder, along with ds
file)
--
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