What are the inherent benefits/detriments of deploying ServiceMix as a standalone product versus deploying it as a SAR or WAR under JBoss or some other application server? From my experience using JBoss there are potential issues or questions that arise:
1) Class Loading - I have experienced many class loading issues running ServiceMix under JBoss's universal class sharing system. For example, Hibernate is included in JBoss's lib directory as one version, but your Service Unit may need a higher version of it. Seems that ServiceMix ends up picking up the top most version (JBoss's). 2) Clustering - Using standard load balanced clustering with Apache and JBoss seems to not give the most reliability in terms of internal ServiceMix message communications between services. It would seem that using JMSFlow would be a more reliable way of achieving clustering with ServiceMix. But how do you marry the two when deploying ServiceMix under JBoss? Would this suggest that a standalone deployment is in order? Thanks, -Jeff -- View this message in context: http://www.nabble.com/ServiceMix-Deployment---Standalone-Vs.-JBoss-tf4536093s12049.html#a12946007 Sent from the ServiceMix - User mailing list archive at Nabble.com.
