I would try this technique:
Create a .esb archive for my generic actions (called generic_actions.esb), in the META-INF folder drop in an empty jboss-esb.xml
<?xml version = "1.0" encoding = "UTF-8"?> <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" parameterReloadSecs="5"> </jbossesb>
Use the jbpm.esb or jbrules.esb as an example of this kind of thing.
Note: I didn't try this trick just yet but I think it will work.
Please try and let us know about your findings.
Well basically you have 2 options:
1. Like you suggested add them as a jar to the jbossesb.sar/lib folder
2. Like Burr says add then in your.esb, then if you want to access them in
another .esb archive make sure to reference your.esb in the deployment.xml to take care of dependencies (deployment order)
Personally I like option 2 better, since it is easier to understand your dependency deployment. Typically your actions will come with their own specific jar dependency, so this way you can keep things organized.