14 Replies Latest reply on Jan 11, 2010 2:38 PM by Ralph Soika

    EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)

    Brian Cowdery Newbie

      Hi All...

      I have a core jar that contains the majority of our business objects as EJB3 entity beans and some simple EJB3 Stateless DAO beans (see Hibernates suggested DAO pattern - caveat emptor example/GenericDAO). This is packaged as objectmodel-core.jar

      In most cases this jar is packaged in a deployable EAR as an EJB jar, however we have some applications that use the defined business objects as POJO's and not EJB entity beans (no usage of @EJB, @Resource or any other type of injection - no usage of persistance units, entity managers and the like... pure POJO).

      In this case we have an application.xml that looks like

      <?xml version="1.0" encoding="UTF-8"?>
      <application xmlns="http://java.sun.com/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
       version="5">
       <module>
       <web>
       <web-uri>webapp.war</web-uri>
       <context-root>/application-web</context-root>
       </web>
       </module>
      
       <library-directory>lib</library-directory>
      </application>


      with objectmodel-core.jar included in the library-directory

      On deployment to JBoss 5.0.1.GA i get an exception stating that it can't find persistence unit named 'null':

      2009-05-05 12:43:08,797 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Real: name=vfszip:/data/apps/jboss-5.0.1.GA/server/jb5-cluster-node0/deploy/subscription.ear/ state=PreReal mode=Manual requiredState=Real
      org.jboss.deployers.spi.DeploymentException: Error deploying subscription.ear: Container jboss.j2ee:ear=subscription.ear,jar=application.ear,name=AnswerDAOImpl,service=EJB3 failed to resolve persistence unit null
       at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:201)
       at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:103)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
       at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.IllegalArgumentException: Container jboss.j2ee:ear=subscription.ear,jar=subscription.ear,name=AnswerDAOImpl,service=EJB3 failed to resolve persistence unit null
       at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:135)
       at org.jboss.injection.PersistenceContextHandler.loadXml(PersistenceContextHandler.java:76)
       at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:588)
       at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:415)
       at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:523)
       at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:194)
       ... 27 more
      Caused by: java.lang.IllegalArgumentException: Can't find a persistence unit named 'null' in AbstractVFSDeploymentContext@2127445{vfszip:/data/apps/jboss-5.0.1.GA/server/jb5-cluster-node0/deploy/subscription.ear/}
       at org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107)
       at org.jboss.ejb3.Ejb3Deployment.resolvePersistenceUnitSupplier(Ejb3Deployment.java:720)
       at org.jboss.ejb3.EJBContainer.resolvePersistenceUnitSupplier(EJBContainer.java:1428)
       at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:130)
       ... 32 more




      There are zero usages of AnswerDAOImpl or its service interface, and absolutely no usages of any Entity beans save for one single class being used as a simple POJO.

      This worked in JBoss 4.2.2.GA so I'm not sure whats going on. IMHO JBoss's deployment scanner shouldn't be touching this jar at all as its not referenced by the application.xml ...

      Anyone have any idea's whats going on here? how can I deploy this application without JBoss attempting to deploy the persistance unit (i've tried removing all persistence.xml and like configuration files from the jar - no dice).

      Thanks for your help.
      -Brian

        • 1. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
          jaikiran pai Master

           

          org.jboss.deployers.spi.DeploymentException: Error deploying subscription.ear: Container jboss.j2ee:ear=subscription.ear,jar=application.ear,name=AnswerDAOImpl,service=EJB3


          1) It's strange that the log mentions jar=application.ear. Is there an application.ear inside the subscription.ear?

          2) I think the disabling of scanning of lib folder in an EAR, is still an issue http://www.jboss.org/index.html?module=bb&op=viewtopic&t=143590

          • 2. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
            Brian Cowdery Newbie

            Sorry, i tried to change all those "subscription.ear" references to "application.ear" (i was trying to keep the example as generic as possible) but i must have missed one.

            Looks like scanning of EAR lib directories is already disabled in the metadata-deployer-jboss-beans.xml configuration file (EarLibExcludeDeployer).

            The post you referenced was never resolved either, fortunately the poster created a bug (https://jira.jboss.org/jira/browse/JBAS-6842) which seems like it will encompass this issue once its resolved. I'll be running some tests with JBoss-5.1.0.CR1 to see if maybe this problem was resolved with the newer release of Jboss Deployers.

            But chances are I'll just have to live with it and watch the JIRA bug for a resolution.

            • 3. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
              Ralph Soika Apprentice

              Hi,

              I have the same issue running on JBoss 5.1.0.GA_j6.
              I try to deploy an EAR with Entity EJBs contained in a shared jar located in the /lib folder of my ear.
              I get the following error message during deployment:

              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@25040105{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/}
              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@25040105{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/}
              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@14529946{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/imixs-workflow-jsf-sample-ejb-0.0.1-SNAPSHOT.jar/}
              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@14529946{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/imixs-workflow-jsf-sample-ejb-0.0.1-SNAPSHOT.jar/}
              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@14529946{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/imixs-workflow-jsf-sample-ejb-0.0.1-SNAPSHOT.jar/}
              15:25:49,501 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@14529946{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/imixs-workflow-jsf-sample-ejb-0.0.1-SNAPSHOT.jar/}
              15:25:49,599 ERROR [Ejb3Deployment] Exception while processing container metadata for EJB: EntityServiceBean in unit: imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear
              15:25:49,599 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/ state=PreReal mode=Manual requiredState=Real
              org.jboss.deployers.spi.DeploymentException: Error deploying imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear: Exception while processing container metadata for EJB: EntityServiceBean in unit: imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear
               at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196)
               at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99)
               at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
               at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
               at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
               at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
               at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
               at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
               at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
               at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
               at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
               at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
               at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
               at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
               at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
               at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
               at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
               at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
               at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
               at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
               at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
               at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
               at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
               at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
               at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
               at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
               at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
               at java.lang.Thread.run(Thread.java:636)
              Caused by: java.lang.Exception: Exception while processing container metadata for EJB: EntityServiceBean in unit: imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear
               at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:549)
               at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189)
               ... 27 more
              Caused by: java.lang.IllegalArgumentException: Container jboss.j2ee:ear=imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear,jar=imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear,name=EntityServiceBean,service=EJB3 failed to resolve persistence unit org.imixs.workflow.jee.jpa
               at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:135)
               at org.jboss.injection.PersistenceContextHandler.loadXml(PersistenceContextHandler.java:76)
               at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:588)
               at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418)
               at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527)
               ... 28 more
              Caused by: java.lang.IllegalArgumentException: Can't find a persistence unit named 'org.imixs.workflow.jee.jpa' in AbstractVFSDeploymentContext@25040105{vfszip:/opt/jboss-5.1.0.GA_j6/server/imixs/deploy/imixs-workflow-jsf-sample-ear-0.0.1-SNAPSHOT.ear/}
               at org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107)
               at org.jboss.ejb3.Ejb3Deployment.resolvePersistenceUnitSupplier(Ejb3Deployment.java:770)
               at org.jboss.ejb3.EJBContainer.resolvePersistenceUnitSupplier(EJBContainer.java:1428)
               at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:130)
               ... 32 more
              


              I did a lot of search in forums but I still found no solution.
              Has anybody a hint what I can do?
              It seams that the deployer did not scan the jars in the /lib folder of my EAR.

              thanks for any help
              Ralph


              • 4. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                jaikiran pai Master

                 

                I try to deploy an EAR with Entity EJBs

                You mean JPA entities right and *not* EJB2.x entity beans.

                contained in a shared jar located in the /lib folder of my ear.


                If they are "deployments" and not just plain jar files then place them at the root of the ear instead of the lib folder.


                • 5. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                  Ralph Soika Apprentice

                  Hi Jaikiran,
                  yes I mean JPA entities. And yes, they are just plain jar files without ejb deployment descriptor. I am deploying a separate EJB Module in my EAR which defines session EJBs and also the persistence.xml with the definition of my persistence unit.

                  So my ear folder structure looks like this:

                  /
                  +- lib/
                  | +- imixs-workflow-api-x.x.x.jar
                  | +- imixs-workflow-jee-x.x.x.jar (contains the JPA entity beans)
                  | +- imixs-workflow-jee-impl-x.x.x.jar (contains EJB 3.0 Session beans)
                  +- my_ejb_module.jar (contains ejb-jar.xml and persistence.xml)
                  +- my_web_module.war
                  +- ...


                  The project is deployable on glassfish successfully.
                  To me it looks like that scanning of the /lib folder did not happen during deployment. Did I need any special descriptor/properties? I read about that this problem was an issue in version 4.x.

                  The ear is part of the imixs workflow project so you can download the application if this would help you understanding my problem:
                  https://imixs-workflow.dev.java.net/servlets/ProjectDocumentList

                  thanks for help
                  ralph

                  • 6. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                    jaikiran pai Master

                    Ralph,

                    I looked at that application and it's packaging looks invalid on one count and a bit weird on another count.

                    The invalid part is - the persistence.xml is deployed through the META-INF of the my_ejb_module.jar. Which means that, as per the EJB3 spec, the persistence unit is scoped only to that jar and will not be visible outside it. So you can't inject using @PersistenceContext from some other jar (imixs-workflow-jee-impl-x.x.x.jar). If you want the persistence unit to be visible to all components in the ear, then you will have to place the persistence.xml in the .ear/META-INF folder.

                    The weird part about the packaging is - the my_ejb_module.jar is mapped as a EJB module and contains only the descriptors (ejb-jar.xml, jboss.xml etc..). No classes within that jar. The EJB interfaces and the implementations are then packaged in imixs-workflow-jee-x.x.x.jar, imixs-workflow-jee-impl-x.x.x.jar and placed in the .ear/lib folder. This is causing issues with the EJB3 deployers. Ideally, the bean implementations should be outside the lib folder, at the root of the ear. Why not package those implementations in the my_ejb_module.jar?


                    • 7. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                      Ralph Soika Apprentice

                      Jaikiran,
                      thanks for your help. Yes when I put the persistence.xml into the .ear it looks much better. The deployer now recognizes the entities and so I take one step forward... :-)

                      "jaikiran" wrote:

                      The weird part about the packaging is - the my_ejb_module.jar is mapped as a EJB module and contains only the descriptors (ejb-jar.xml, jboss.xml etc..). No classes within that jar.


                      I know this looks not typical for an jee project, but I think it should be a typical way deploying existing JEE components. The reason for that ear layout is, that I want to provide developers of workflow applications with a EJB based workflow component. This component is part of the imixs wokflow project and packaged into the imixs-workflow-jee-x.x.x and imixs-workflow-jee-impl-x.x.x jars.
                      So if you plan to add Imixs workflow components into your JEE Web project there should be no need to add sources/classes into the EJB Module or deal with the whole EJB stuff. The developer should only declare a few descriptors. So the JEE Project becomes very compact.
                      My vision is that the application developer concentrates on the GUI and add only some Richfaces libs and some business logic bundled in ejb-jars.
                      I think this is one of the concepts behind JEE component architecture. And I did not understand why we found so much cool GUI components like RichFaces but no business components which helps developers to speed up the application development.

                      Maybe this idea becomes more clear if you look at one tutorial I wrote about the usage of my maven archetype:

                      http://www-02.imixs.com/roller/imixsworkflow/entry/building_a_imixs_workflow_webapp2

                      you see - I want to attest that not only RubyOnRails developers are speedy ;-)

                      • 8. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                        Ralph Soika Apprentice

                        After all I was not able to deploy my EAR with the provided EJB jars successfully. But I found the following Bug report which seems to be similar to my general deployment problem:
                        https://jira.jboss.org/jira/browse/JBAS-6842

                        So I installed now JBoss AS 6.0.0 M1 and now the project with EJBs and JPA Entities deploys successfully without errors ! Also when the EJB modul only contains the ejb-jar.xml and the persistence.xml. All implementations classes are provided by jars placed in the /lib folder of my EAR.

                        So it seems that the general EAR Folder layout is ok for JBoss AS 6.0.

                        So for now I will go further with JBoss 6.0 - I found some new problems during deployment with my current Faclets and WebService configuration ;-)

                        • 9. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                          jaikiran pai Master

                           

                          "rsoika" wrote:


                          So I installed now JBoss AS 6.0.0 M1 and now the project with EJBs and JPA Entities deploys successfully without errors ! Also when the EJB modul only contains the ejb-jar.xml and the persistence.xml. All implementations classes are provided by jars placed in the /lib folder of my EAR.


                          That's good to know. Thanks for reporting.


                          • 10. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                            Nicholas Folts Newbie
                            I was wondering if anyone has figured out a way to get this to work? We have multiple WARS/EARS that use our JAR containing our EJBs and persistence.xml and we don't want to have to have the jar in every one of them... This file struture works great in JBoss 4.2.3, but haven't been able to get it to work in 5.1, and we don't want to rely on JBoss 6 as it is only a milestone release...
                            • 11. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                              jaikiran pai Master
                              Can you explain your packaging a bit more in detail including what issue you are running into?
                              • 12. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                                Ralph Soika Apprentice

                                Hi,

                                I think the EAR structure we are talking about looks like the following:

                                / 
                                +- lib/
                                | +- imixs-workflow-api-x.x.x.jar
                                | +- imixs-workflow-jee-x.x.x.jar (contains the JPA entity beans)
                                | +- imixs-workflow-jee-impl-x.x.x.jar (contains EJB 3.0 Session beans)
                                +- my_ejb_module.jar (contains ejb-jar.xml and persistence.xml)
                                +- my_web_module.war
                                +- ...

                                 

                                This folder layout is not typical for a simple EAR example discussed in most of the ear tutorials. But I think it is typical for more complex projects where you need to reuse a EJB or JPA module independent form one specific project. So the goal is to share a JAR with EJBs in different projects. And this seems to be supported by the JEE6 spec if you put these jars into the /lib folder.

                                To control which of the EJBs (form the shared lib) are used in project specific way I overwrite the annotations in the ejb-jar.xml in the project specific EJB module (my_ejb_module.jar).

                                 

                                If this kind of packaging is wrong and not JEE6 conform - what would be the best way to solve such a deployment problem?

                                • 13. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                                  jaikiran pai Master

                                  Ralph, have you tried this against JBoss AS 6.0.M1? I think there was a bug fix in that version which would probably solve your issue. If you are running into issues even on AS 6.0.0.M1, then please post the details and we'll look into it in more detail.

                                  • 14. Re: EJB jar cannot be deployed as a library (JBoss 5.0.1.GA)
                                    Ralph Soika Apprentice

                                    yes my last test was with jboss AS 6.0.0.M1. I noticed that 6.0.0.M1 have some improvements in handling JPA bundles deployed in ear/lib folder.

                                    Currently I have stopped testing because I am a little bit bussy. But I will post my results here when I continue testing.....

                                     

                                    ralph