+1 for several distributions. However I see several problems: * where to put the samples: some use the standard JBI deployment (SU + SA) and other only use a static spring configuration with lightweight components. * we need to provide a clean documentation about integration styles: servicemix standalone, in a web app, embedded so that users can choose the needed distribution
On 7/18/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
I have been thinking over the restructuring that we have been discussing and I'm wondering whether we should look at create a couple of flavours of distribution, so that in place of a big install we have: Server - Just the Core Server (no components) Server/Components - Core Server and Components Geronimo Package - Core Server with everything needed to deploy to geronimo
For the Geronimo package, I think that a Geronimo plugin would be the best way to do that, as Aaron pointed in another thread. JBoss Package (off-site) - Core Server with everything needed to deploy to
JBoss Components - Just the components Also I'm wondering whether we should look at the archetypes as a way to offer the functionality such as:
+1 Cheers, Guillaume Nodet ServiceMix Embedded in a Web Application
ServiceMix Embedded in a simple Application ServiceMix Embedding with Spring I have been adding archetypes to get things started for the components we have now and intend to continue with that. Also I'm thinking we could fix up the lwcontainers (I'm getting to it) and then create archetypes for each of the components so that we are able to provide a little bit of quick start information. Cheers Philip
