Niclas Hedhman wrote:
On Sat, Nov 8, 2008 at 3:52 AM, Greg Trasuk <[EMAIL PROTECTED]> wrote:
Remember that 'transient' and 'local' are two different things. Usually
a transient instance of the service still exports a remote endpoint; it
just doesn't save its state to disk.
Yes, no problem with that. But my lifecycle 'controller' of these
services are running in the same JVM (as part of junit tests), hence
my referral to 'local'.
<historicalPerspective memory="faulty" value="questionable">
The starter kit didn't really support the sort local lifecycle
controllers you are building until 2.1. The basic interfaces were
introduced in 2.0, but at that point the emphasis was on supporting the
configurable service starter command line tool and some of cases that
are important for local controllers had not yet been addressed.
In contrast we had DestroyAdmin in v1.0. At that point it had to be
remote (since 3rd party agents running in the same VM as the service
backend was not part of our model) and by the time 2.1 rolled around it
didn't occur to us to add local admin interfaces.
</historicalPerspective>
