Sorry about the confusion -- I guess the easiest way to explain it is through an example. Case 1: I want to add a new Telnet (or whatever other protocol) gateway to the system. Rather than adding it to the core JBossESB source code, I would like to be able to deploy the new implementation such that all of the impl code is contained in a separate jar. The JBossESB deployer would detect when the jar is added to the deploy directory and would add the gateway impl to the list it supports. Some of the meta-information in the jar would indicate how the new gateway would be referenced from the jboss-esb.xml. It is my understanding that EPRs are lightweight facades that provide info to the underlying gateway impl, so I was suggesting that the available EPR classes for an impl would be listed in the jar metadata. So, I would create my impl, jar up the libs/classes/metadata, drop telnetImpl.jar into the deploy directory, and all deployments could reference the new technology without changes to the core libs. Case 2: I want to replace the FTP gateway/EPRs/etc included with JBossESB with my own impl. If the packaged implementations for file, FTP, JMS, etc are just jars in the jbossesb.sar folder, I could build my own and replace the appropriate jar (i.e ftpImpl.jar) with my new code... preferably without bouncing the server. Does that make more sense? Thanks, Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037715#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...