1 Reply Latest reply on Aug 11, 2014 2:03 PM by Wolf-Dieter Fink

    JBoss static modules interests

    Nicolas Nicolas Newbie



      I migrated my company's JBoss server to JBoss-EAP6 for few months.

      Since this migration, we use static modules for third libraries.

      they allow us to save time during production installations.


      But now, there are developers which want to package all the third libraries in their own EAR.

      Indeed, for them, it's easier to package all their jars/wars in one file and put it in JBoss. Moreover, with this kind of ear they are sure to be able to change the application server without recompiling their ears... (I'm not sure of this argument, I tried in past and I never did it without changes...)


      They don't want to understand the production problems...

      That's why I would like to list all the interests of static modules :


      - Share modules between applications in the JBoss implementation,

      - Only synchronize new modules in production (we use rsync to get static/dynamic modules),

      - Better class loading management?

      - Better performances?


      Can you help me do convince them? Or, if you are not agree with my point of view, can you explain me why (with others arguments that "easier to package", I know it )?


      Thanks in advance,



        • 1. Re: JBoss static modules interests
          Wolf-Dieter Fink Newbie

          Share third party libraries will save memory and you can control the version in the server installation. If you depend on a specific version you are able to use separate versions of the lib and depend the deployed application to it.

          From a performance perspective there is no difference (exept the memory consumption).

          App developers might prefer to have the tested version packed in the application. But if you pack JBoss libraries or EE libs in the application you might run into problems.

          In any case it should be well considered what you do.