I am a bit confused as well, especially in deciding which is the best way to install components and deploy service assemblies.

The static way (using servicemix.xml) seems the easiest to me, however, the xml document can get very large and difficult to read after a while.

If I want to install them at run-time, I have several choices:
- use the lwcontainer for pojos
- use the jbi compliant way for standard components
- programmatically add either components (as often done in the test cases)
- there also used to be the spring client toolkit for pojos, where you could also create jbi compliant installers using maven jbi:jbi - it says it's deprecated, but it still works for me

I am not sure which one to choose, so I will try a number of different ways. BTW, Is there an example of how to create jbi service assemblies and deploy them with a jbi component at run-time?

Thanks,
Stefan


Guillaume Nodet wrote:

Well, I think you have quite well understood these confusing concepts.
I have tried to make them a bit more clear in
http://docs.codehaus.org/display/SM/What+is+a+lightweight+component

Hope this helps,
Guillaume Nodet


On 4/19/06, kahon <[EMAIL PROTECTED]> wrote:
  What's the meaning of a Pojo Component? Then non-Pojo Component?
  And the concept Light-Weighter Component verus Standard component?
  At first I think Components which have a Component Impl extends
ComponentSupport is a Pojo component,and the others are non-Pojo Compnents.
But when I see the ComponentMBeanImpl's pojo attribute and the HttpComponent
instance's activation from source code in the Junit TestCase( in the
servicemix-http project),I find the HttpComponent in that Junit test case
seems like a pojo Component,because the HttpComponent's activation calls to
JBIContainer's method activateComponent(File installationDir, Component
component, String description,
                                       ComponentContextImpl context,
ActivationSpec activationSpec, boolean pojo, boolean binding, boolean
service) with the parameter pojo set true.
   So in this case the HttpComponent is a pojo component? If so,i'm
wondering what's difference of a pojo Component and a non-pojo component?

   As the latter confusion,I think the lightweight component has a
ComponentSupport's subclass,and the the others are standard components.
   Is my view right?
--
View this message in context: 
http://www.nabble.com/some-concepts-in-Servicemix-confused-me---t1472508.html#a3982036
Sent from the ServiceMix - User forum at Nabble.com.



Reply via email to