On Tuesday 19 August 2008 14:01:04 [EMAIL PROTECTED] wrote: Hallo,
> To solve it for my needs I do a bunch of unpleasent inheritance and
> reflection (as each field is private for shutting down - my only huge issue
> with Muse's design) to allow subscriptions and resources to be persisted.
> I have at least 6 of the core files replaced to allow shutting down etc
> which of course implies changes to the muse.xml for configuring them.
>
> I would have to check with my Boss about sharing that code, but I don't see
> a problem, although it would definitely be given "as is". Also the default
> framework does not have a notion of shutting down and then restarting,
> which may also affect your tests.
Thanks for your effort! If not I think I could also use Lenni's approach -
just calling the listening resource "by hand".
Jan
--
Institute for Geoinformatics
[EMAIL PROTECTED] Robert-Koch-Strasse 26-28
+49 251 83-31960 48151 Münster, Germany
signature.asc
Description: This is a digitally signed message part.
