Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7032

Getting invalid deployment on what appears to be valid, a webbeans ear file.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M1
    • Component/s: Deployers
    • Labels:
    • Environment:

      JBoss AS 5.1
      JDK 1.6 u 13
      OpenSuSe 11.1 / SLES 10.2

      Description

      The best description I can give is from the forum.

      Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails.

        Gliffy Diagrams

        1. jboss-app.xml
          0.3 kB
          Shelly McGowan
        2. PrintResourcePathContextListener.class
          2 kB
          Stan Silvert
        3. PrintResourcePathContextListener.java
          2 kB
          Stan Silvert
        4. WhatUpDawg.ear
          6.65 MB
          Stan Silvert
        5. WhatUpDawg.ear
          6.65 MB
          John Ament

          Issue Links

            Activity

            Hide
            meetoblivion John Ament added a comment -

            just wondering, can you provide a demo jboss-app.xml that works around this?

            Show
            meetoblivion John Ament added a comment - just wondering, can you provide a demo jboss-app.xml that works around this?
            Hide
            shelly.mcgowan Shelly McGowan added a comment -

            John, see attached is a jboss-app.xml

            Show
            shelly.mcgowan Shelly McGowan added a comment - John, see attached is a jboss-app.xml
            Hide
            alesj Ales Justin added a comment -

            >> I have found that an EAR which includes SEAM/RF library jars in the EAR/lib directory without a jboss-app.xml

            With any Seam app proper isolation must always be enforced,
            otherwise Seam cannot work properly as its architecture depends on cl isolation.
            e.g. Component::getComponent(name), static usage to get component from anywhere

            WebBeans used to work the same way, but this prevented to be properly used inside OSGi based kernel/container.
            Hence a different approach was used, scope/components per classloader hidden in a proper abstraction.

            Show
            alesj Ales Justin added a comment - >> I have found that an EAR which includes SEAM/RF library jars in the EAR/lib directory without a jboss-app.xml With any Seam app proper isolation must always be enforced, otherwise Seam cannot work properly as its architecture depends on cl isolation. e.g. Component::getComponent(name), static usage to get component from anywhere WebBeans used to work the same way, but this prevented to be properly used inside OSGi based kernel/container. Hence a different approach was used, scope/components per classloader hidden in a proper abstraction.
            Hide
            jason.greene Jason Greene added a comment -

            This is NOT a blocker, because the correct solution is to use isolation, which will be on by default in 5.2.

            Show
            jason.greene Jason Greene added a comment - This is NOT a blocker, because the correct solution is to use isolation, which will be on by default in 5.2.
            Hide
            jason.greene Jason Greene added a comment -

            EAR isolation is now on by default, so this should be resolved.

            Show
            jason.greene Jason Greene added a comment - EAR isolation is now on by default, so this should be resolved.

              People

              • Assignee:
                shelly.mcgowan Shelly McGowan
                Reporter:
                meetoblivion John Ament
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development