2 Replies Latest reply on Jul 3, 2005 2:32 PM by samfra

    deployment issue in 4.0.2 for multiple sar

    yangju

      In jboss 4.0.2, I got class loader not found error when I tried to deploy multiple sars. I have A.sar which needs classes contained in B.sar. A.sar also contains mbeans that depends on services defined in B.sar. However, when jboss is started, A.sar is loaded first and it could not find needed classes and it just gave up. I would expect that A.sar deployment should wait until all other sars are deployed.

      I don't have classloader repository defined for A.sar and B.sar. So I assume they use the same default class loader repository.

      This was not a problem in 3.05, if I remeber correlty.

      Can anyone shed some light on me? Is there any walk around?

      Thanks.

      Richard

        • 1. Re: deployment issue in 4.0.2 for multiple sar
          starksm64

          Dependencies never have been at the class loading level. Factor out the common classes to a seperate jar referenced via the sar jboss-service.xml classpath element.

          • 2. Re: deployment issue in 4.0.2 for multiple sar
            samfra

            Hello,

            I've got the same problem !

            I also have B.sar that uses A.sar classes (but not A.sar, that uses B.sar).

            If you deploy your sars, one by one... it's OK !

            unfortunately, I'm still trying to find a solution...

            I've got :

            00.jar
            01.har
            A.sar
            B.sar
            W.war

            and each level needs the classes from the other....

            if I deploy them one by one, as I said, it's OK.

            or, if I do like that :

            ../lib/00.jar
            ../lib/01.har (.class-files)
            01.har (without class files, only hbm)
            A.sar
            B.sar
            W.war

            it's OK.