Hi Dasarath,
BTW, did you look at our recent patch which adds a second configuration
option to specify the kandula services context URL to use?
this patch I'm still not sure what you'll are shooting for-- what I feel is that
the requirement is met by the current code. may be if you could put it in
another way/example may be that will help.
With the existing code base an application can pass the desired
activation service EPR to begin().
We felt it was more convenient to allow a default activation service EPR
to be specified in the configuration file; applications may still use
other activation services by passing an EPR to begin().
Well, thats it ;-)
If you wonder why one would want to use a remote activation service:
this allows initiating applications to be "firewalled" from the actual
participants; only the coordinator specified in the kandula.properties
must be able to send messages to the initiator.
Have a nice week*end* and good luck for your tests ;-),
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
