<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Camel integration input requested
</h3>
<span style="margin-bottom: 10px;">
reply from <a href="http://community.jboss.org/people/dward">David Ward</a> in <i>JBoss ESB Development</i> - <a href="http://community.jboss.org/message/548554#548554">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><blockquote class="jive-quote">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?</blockquote><p>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.  <span> ;) </span>  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.</p><blockquote class="jive-quote">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.</blockquote><p>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.</p><blockquote class="jive-quote">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.</blockquote><p>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.</p><blockquote class="jive-quote"><p>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". ;-) </p></blockquote><p>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 again, we need to wrap up the other 4.9 issues first.</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/548554#548554">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss ESB Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2032">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>