I am running into an issue with classloading in the ActionProcessingPipeline. In particular, I have reusable action classes packaged into a sar separate from the jbossesb.sar. My standalone config (jboss-esb.xml) references an action class loaded in the other sar. When the config is loaded at startup (the pipeline eager-loads the action classes on initialization), the other sar has not been loaded, resulting in a ClassNotFoundException. If I move the jar with custom actions into jbossesb.sar, everything works fine. I am wondering if the ActionProcessingPipeline should lazy-load the action classes so that everything has a chance to load. This has the side-effect of not reporting classloading errors until the first time the action chain is used -- which may be a bad thing. Any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030791#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...