Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-1348

New Seam EAR projects don't include jboss-app.xml, causing classloader confusion for the inexperienced

    Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.0.0.CR1
    • Fix Version/s: 2.0.0.GA
    • Component/s: seam2
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

          1. screenshot-1.jpg
            screenshot-1.jpg
            105 kB
          2. screenshot-2.jpg
            screenshot-2.jpg
            85 kB
          3. screenshot-3.jpg
            screenshot-3.jpg
            67 kB
          4. screenshot-4.jpg
            screenshot-4.jpg
            103 kB

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                gcomnz Marcus Adair
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: