1 2 3 Previous Next 33 Replies Latest reply on Feb 3, 2011 1:42 PM by jumanji4u Go to original post
      • 30. Re: Camel integration input requested
        o Is the jboss.esb lib directory the only recommended place to put component libraries?  It's certainly possible to put it in one of the higher level AS lib directories.  Is it possible to bundle them with the ESB application?  Do we recommend against these other methods?

        Right now it is recommended to put component libraries in server/default/deploy/jbossesb.sar/lib/ for AS4 and server/default/deployers/esb.deployer/lib/ for AS5, because that is all that has been tested with so far.    I might go back and give the other options a try if I have time, but right now there are pleny of other 4.9 issues that need to be addressed first.

        o Component jars in the jboss.esb lib directory will be loaded during server startup.  Correct me if I'm wrong, but adding additional jars here will require the ESB sar to be redeployed or (more likely) the server restarted.  Might want to point this out.

        Are you saying add it to the wiki page?  That's fine.  I will note that I don't think that this is a problem.  If you are adding component jars, then you are most likely adding non-trivial (aka: important) functionality - functionality that in the real world should go through an organization's standard test + release cycles.  "Hot deploy" is a nice feature for developers, but in my experience production systems get "bounced" when adding this level of functionality.

        o Having a single class loading space for additional components means that there can only be one version of a component in the ESB runtime at any given time.  Probably worth mentioning this point.

        True, but this would not be the first place in the ESB (or AS, for that matter) where there is "a" version of a library.

        o There is a distinct possibility that one of the many camel components will include jars that we already have in the ESB or the AS already.  If the versions of these dependencies are different than things can go boom.  Isolating the class space with class loader repository might be one way to address this.  Another way to address it is to say "YMMV". ;-)

        Jumping through the dependency hoops is something that we all are used to.  I'm not saying we shouldn't try to make this easier, or try things like class loader isolation and such - we definitely should.  But what is there now works, and again, we need to wrap up the other 4.9 issues first.

        • 31. Re: Camel integration input requested

          I probably should have prefaced my feedback by saying that I don't think it requires functionality changes or even further testing right now.  Probably just a 3-4 bullet summary something along the lines of:


          • When installing additional Camel components, it is recommended that the component jars and any dependenies are placed in the JBoss ESB SAR's lib directory
            • AS 4: .../server/default/deploy/jbossesb.sar/lib/
            • AS 5: .../server/default/deployers/esb.deployer/lib/
          • While component jars can be installed in alternate locations (e.g. server lib, or within an ESB application), this has not been tested.
          • A restart of the ESB server will be required afer installing the component jars before the component's URI can be used by the Camel gateway


          We can add class loader scoping to the above instructions when we get around to it.  Or maybe someone in the community that's interested will do it and post their experience to the forum.



          • 32. Re: Camel integration input requested

            Fair enough.  I just added the following note to CamelGateway: Using non-core Components:


            Note: When installing additional Camel Components, the directories listed above are the recommended location for the Component jar libraries and any of their dependent jar libraries.  Whereas installing these libraries in other directories available to JBoss might be possible, it has not been tested, and thus not recommended.  Finally, be aware that a restart of the ESB server will be required afer installing the Component jars before the Component's URI can be used by the CamelGateway.

            • 33. Camel integration input requested

              Very interesting and great Info. thanks guys

              1 2 3 Previous Next