On 3/23/07, aharsola <[EMAIL PROTECTED]> wrote:
Hi, I am using ServiceMix 3.0.1 First, As I understand, to acess JBI components deployed to a ServiceMix container from outside the container, ServiceMix provide two options a) DefaultServiceMixClient : Caller and ServiceMix are in the same JVM b) RemoteServiceMixClient : Caller and ServiceMix are in different JVM As I understand from code, both clients start ServiceMix in a embedded mode with its message broker pointing to the broker of the parent ServiceMix container. Is this always the case? Why client has to start the servicemix container when there is already a container running?
The DefaultServicMixClient reuses an existing JBI container that you have to supply. The RemoteServiceMixClient uses clustering and thus starts its own embedded container, but it should start with a minimal configuration. Second,
If I have to embedd ServiceMix inside a web application, what needs to be done? How can I install components and deploy service units to the embedded servicemix container? The servicemix-web (3.0.1) example looks like does not support standard JBI deployment.
Take a look at the apache-servicemix-web distribution, which is a web application embedding a ServiceMix container which fully supports JBI deployment. The war is available on the download page. Though the servicemix-web has not been designed for that, it should already support JBI deployment using ant tasks (the hot deploy service is disabled iirc, but you could enable it). Any ideas?
Regards, Amit -- View this message in context: http://www.nabble.com/Please-help---Using-ServiceMix-Client-tf3451961s12049.html#a9629078 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
