I'm thinking the simplest solution is the best. The least amount of parts
that need to be maintained/versioned is always better. That
said...deploying ServiceMix as the "server" would be best - especially from
an external integration perspective too.
On 8/4/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
>
> On 8/3/07, Jeffrey Puro <[EMAIL PROTECTED]> wrote:
> > Is it considered better to deploy ServiceMix as a standalone product as
> > opposed to having it deployed in JBoss AS?
>
> Because ServiceMix is a deployment platform, it provides multiple
> deployment models for maximum flexibility. One deployment model is not
> necessarily better than another one. It's more a matter of what fits
> the given situation best which is oftentimes just simply a judgment
> call.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
>
--
Kit Plummer
Nobody-in-Charge @ Black:Hole:Logic
http://www.blackholelogic.com
