1 Reply Latest reply on Jul 9, 2011 9:24 AM by jaikiran pai

    Best Practice for Managing Module Manifests?

    daman Newbie

      Hi

      I’m looking at migrating a fairly large project to AS7 (15 modules, each with many dependencies, and some modules depending on others).

      I’ve read:

      https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7

      https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7

       

      What I’m looking for is a best practice approach to managing my manifests. The thread ending here:

      https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7

      seems to imply that Maven is not the best approach. And the “try to deploy, see where it breaks and then fix” advocated in the migration guide seems fairly naïve and unscalable for the amount of stuff I want to migrate.

       

      Can anyone point me to a better approach? Create a module with all the dependencies bundled in it and just reference that? Not pretty but quick...

        • 1. Re: Best Practice for Managing Module Manifests?
          jaikiran pai Master

          Daman, welcome to the forums!

           

           

          daman wrote:

           

          Hi

          I’m looking at migrating a fairly large project to AS7 (15 modules, each with many dependencies, and some modules depending on others).

          Before we get into the details of JBoss Modules, can you tell us what you mean by "modules" in your case? Are you talking of Java EE modules like a web module, EJB module etc...? Is it a Java EE application? If yes, then in most cases you don't have to create JBoss Modules for your application. Packaging the application in the Java EE spec specified way should usually work, unless you want to depend on a JBoss Module.