[jbosstools-issues] [JBoss JIRA] Reopened: (JBIDE-1348) New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced

[Marcus Adair (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-1348?page=all ]

Marcus Adair reopened JBIDE-1348:
---------------------------------

             
I've attached screen shots of the process I used to create the project. A couple notes:

-- The only choice I selected that was not default was to select "Dynamic Web Project with Seam 2.0 (technology preview)" in screenshot 2

-- And, now to be Captain Obvious (to myself), I filed this ticket under JBIDE, but I actually don't have any proof that it affects anything other than RHDS CR1, I'm sorry about that

-- I have doubled checked on the file system that the deployment does not contain anything other than an application.xml in the testproj-ear.ear/META-INF directory (or anywhere else)

-- I'm using Seam 2.0.0.GA

> 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