Hi Jan, Sorry, I misunderstood, that code is part of the problem.
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. cheers, Chris -----Original Message----- From: Jan Torben Heuer [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2008 1:46 PM To: [email protected] Subject: Re: Listening for resource shutdown? On Thursday 07 August 2008 14:37:37 [EMAIL PROTECTED] wrote: Hallo, > ResourceManagerListener and the ResourceManager can help here. All > resources removals will trigger the callback functions so you have to > filter yourself. Because I got notification for all but my self-instantiated resources I took a look at the SimpleResource. I found this code in the shutdown method: // // remove resource visibility // // sanity check: make sure the resource was put in manager. this may // not be the case for internal resources // if (manager.getResource(_epr) != null) manager.removeResource(_epr); the if-clause didn't match in my case so, what do I have to do to put my self-instantiated resource into the manager? I do: /* create new resource */ newPublicationEndpoint = manager.createResource(publisherRegistrationManagerEndpoint); Jan -- Institute for Geoinformatics [EMAIL PROTECTED] Robert-Koch-Strasse 26-28 +49 251 83-31960 48151 Münster, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
