I added most of the remaining maven assemblies. I ran into a couple of questions while creating them.
Metatype (API) and Spring (impl) only generate one artifact, should these be packaged as metatype-api and spring-impl? Or can they just use the default maven packaging to create a single jar?
The container sub-project has a lot of parts, is there a way to simplify this? Like having a single SPI artifact for all of this subproject?
Also, I am planning to remove the ant build scripts from SVN tonight as long as there are no objections.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030804#4030804
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030804
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#4030791
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030791