Kurt, That sounds like exactly what I was looking for. Thanks for the clarification! For the registration of non-ESB-aware endpoints, it seems like the EPR instances (created from the -esb.xml) could have provider category and provider name properties added in the schema. The EPR instances that have those properties would be added to the registry on startup and would be discoverable by other components. Deployment of the actual providers that implement functionality for the EPRs is something I have been wondering about too. Right now, the providers for file, FTP, JMS, etc are tightly coupled to the framework itself. It seems like the providers should be deployed separately in their own SARs, and hot-deployed by the ESB. The SAR would include all of the implementation code and some kind of descriptor that contains a list of the EPRs available from the provider. Each EPR listed would have a unique identifier so that it could be referenced from the -esb.xml to create an EPR instance (would require using the generic schema elements rather than the provider-specific ones). It sounds like a lot of work, but I think it would make contributing new providers to the ESB much easier. Thanks, Derek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036041#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...