Hi Harbeer,
my comments inline:
I have some questions.
1) Does JBI support normal java based invoking of methods like OSGI. I want
to keep the platform and connector seperate as the platform will be deployed
only once. But tomorrow if any new webservice we want to talk, then we have
to add a connector bundle for that also without hurting the platform code.
You have two ways to achieve this:
- use servicemix-bean: this service engine uses a POJO/Bean to manage in
messages. You can deploy several servicemix-bean endpoints.
- you can create your own JBI component implementing the same business
logic as you made in OSGi.
2) How JBI can be better than OSGI in this problem.
To be honest, I think that if you haven't big JBI requirements, the best
implementation is OSGi.
I don't think that JBI is better than OSGi for your requirements.
Regards
JB
I am also attaching a image showing the requirement of the project in terms
of enterprise integration pattern components
http://old.nabble.com/file/p28152691/ExecuteOperation.png
ExecuteOperation.png .
The content based router is the platform which delegates the call to the
correct connector. The session manager keeps the instances of connectors
with it.
With Regards
Harbeer Kadian
