1 Reply Latest reply on Aug 7, 2008 10:07 AM by Gert Vanthienen

    ESB 4.0: shared libraries

    Andre Skusa Newbie

      Hi there,


      this is a question regarding the announcement, that in ServiceMix 4 the shared library mechanism will be no longer used. Is there any replacement for it or does any JBI application now have to contain all the libraries it uses in itself?


      Or would another way be to access OSGi bundled java libs from within a jbi component/service?


      Thanks in advance, best regards,


      Andre Skusa

        • 1. Re: ESB 4.0: shared libraries
          Gert Vanthienen Novice

          Andre Skusa,


          We no longer need the shared library approach for our own components because we will leverage the OSGi classloading mechanisms for that.  You will still be able to deploy SL to ESB4 if you want, ESB 4 will remain compatible with JBI.


          For your own codebase, if you add a bundle to provide the shared code (i.e. it has an Export-Packages for the right packages), this will be available from within a JBI service/component as well.  Using OSGi packaging instead of JBI packaging will allow you to use even more fine-grained control over imports (e.g. for using multiple library versions).