[
http://jira.jboss.com/jira/browse/JBIDE-1348?page=all ]
Max Andersen resolved JBIDE-1348.
---------------------------------
Resolution: Done
somehow jboss-app.xml was removed for seam2 (I was looking at an older build when testing
it - sorry)
Can't recall why it was removed so brought it back + cleaned up the jar list to fit
100% with what seamgen generates.
Marcus - if you could please test this with the next nightly build that seam2 ear/war
works for you then I would very much appreicate that.
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
Fix For: 2.0.0.GA
Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg,
screenshot-4.jpg
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