[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1348) New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced
Max Andersen (JIRA)
jira-events at lists.jboss.org
Wed Nov 21 11:39:31 EST 2007
[ http://jira.jboss.com/jira/browse/JBIDE-1348?page=comments#action_12388652 ]
Max Andersen commented on JBIDE-1348:
-------------------------------------
what do you mean ?
META-INF/jboss-app.xml is explicitly created with the following content:
<jboss-app>
<loader-repository>
seam.jboss.org:loader=xyz-ear.ear
</loader-repository>
</jboss-app>
what version of seam are you using?
> New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-1348
> URL: http://jira.jboss.com/jira/browse/JBIDE-1348
> Project: JBoss Tools
> Issue Type: Feature Request
> Components: Seam
> Affects Versions: 2.0.0.CR1
> Reporter: Marcus Adair
>
> When a new Seam EAR project is created with JBoss Tools or RHDS, there is no jboss-app.xml included in the EAR META-INF directory. An inexperienced user then creating and deploying additional projects will be confused to find that both classloader namespace and component namespace conflicts occur.
> I think it's fairly well established that these classloader conflicts are a source of particularly disheartening pain for new users to a Java application server platform, whether or not one agrees with a particular implementation. Generating new projects in their own classloader namespace will go a long way toward reducing the bloodletting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list