Well, you also loose the following things :)

        * Karaf - The kernel where most of these things are tested.
        * JRE Setup
        * Class exposure of things JVM vs. 3rd Party (Think XML)
        * Class ordering tools
        * KAR
        * OBR
        * MVN integrations
        * JBI
        * File deployment

        * Visibility integrations (karaf commands, webconsole)
        * SSH
        * Partly probably JMX

        * JAAS integrations
        * Integrated Aries / Geronimo testing
        * Encrypted properties
        * LDAP properties
        * Camel Testing
        * CXF Testing
        * ActiveMQ Testing
        * All of the frameworks Camel bring in tests.

        * Tutorials that work
        
Besides that, yes you are 100% correct, nothing to be gained :)

On Feb 25, 2012, at 8:41 PM, Matt Pavlovich wrote:

> Hi Baleado-
> 
> You could try to build all the frameworks together, but one of the advantages 
> of using ServiceMix, is that you are using a build that is being used by 
> hundreds of other people, and all the dependency versions (and transitive 
> dependencies!) are sorted out.  The management pieces including Maven-based 
> deployments, features, ConfigAdmin.. and the list goes on.  ServiceMix 
> represents the next generation of Application Server technologies.
> 
> Also, the OSGi bits shouldn't be overlooked.  There are a lot of advantages 
> to using Blueprint over Spring and not having to use other heavier J2EE 
> technologies.
> 
> Matt Pavlovich
> 
> On 2/23/12 12:16 PM, Baleado wrote:
>> Thank you guys for your quick replies,
>> 
>> To clarify, basically ServiceMix is an OSGi environment (Apache Karaf) that
>> provides a set of apache frameworks like Apache Camel, Apache CXF and Apache
>> ActiveMQ in a unified platform that supports a legacy/dead JBI specification
>> through NMR.
>> 
>> So if I understand the mainly difference in build a integration solution
>> using ServiceMix or using each framework individualy is the OSGi server.
>> 
>> For example if I want to build a integration solution running inside a
>> Aplication Server I can achieve the same result using each Apache framework
>> individualy, losing all the management facilities that OSGi server offers.
>> 
>> I'm right?
>> 
>> --
>> View this message in context: 
>> http://servicemix.396122.n5.nabble.com/Doubt-about-ServiceMix-architecture-tp5508586p5508888.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to