Currently we create beans for interacting with activemq in each project. So a lot of poolConnectionFactories get created. This creates a lot of connections to activemq and we also must invest a lot to change this configuration. The pro to this aproach is that change can be implemented standalone without affecting other services. Is the con bigger? Should we centralize the beans in a separate war which includes jar for other funtions (if we want to keep our projects small)? This way less beans will be created (only one for a group of projects).
It isn't a Camel issue but I'm looking for advice how to split my wars or how not to split my wars when I use camel and activemq. Bruno Borges wrote > Not sure if this is really a Camel issue, is it? > > Could you please clarify the problem? -- View this message in context: http://camel.465427.n5.nabble.com/large-war-or-several-smaller-wars-tp5732294p5732299.html Sent from the Camel - Users mailing list archive at Nabble.com.
