Sorry for the late feedback.
But multiple component instance, you mean that you want to deploy the
same installer zip file several time in the deploy/hotdeploy directory ?
If it's the case:
1/ it's not possible or you need to change the component name in the RMI
registry (or you will have duplicate name exception).
2/ a component can manage a large number of SU: a SU define an endpoint
on the component. It's multithreaded (manager by the executor
configuration) and can manage large number of messages/endpoints.
Are you sure that it's really the "same" component ? When you talk about
multiple instance of the same component, are you sure that you don't
talk about different endpoints ?
Regards
JB
Thushara Seneviratne wrote:
Any pointer for this ..?
Thanks ,
On Fri, Jan 15, 2010 at 3:39 PM, Thushara Seneviratne <
[email protected]> wrote:
Hi ,
We have a business requirement to create a multiple instance of
same component and each instance should have different endpoints , one
possible scenario is give below
1.) Implement my component ( can be a BC or a SE)
2.) Create a installer and deploy the component ( I think now my component
is registered with NMR with a endpoint)
3.) Create a second instance of a component and register it with
a different endpoint ( for external world it appears like two components )
My problem is how can i create /mange multiple instance of a
single component and how to register separate endpoint for each of these
instances , is there any Servicemix API or any workaround for this ?
I tried with AdminCommandsService API but seems like it's doesn't supports
for that extend.
Thanks,
Thushara
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
