From mailing list thread "How To: deconfigure the registered beans?":
Shashi wrote:
We are using DWR in OSGi environment wherein we have multiple bundles containing dwr configurations and getting loaded dynamically in the Container object available with a web bundle.
This is working like charm.
Currently I am looking to deconfigure the services registered in the container at runtime if a bundle goes down. Using the DwrXmlConfigurator and Container API I can't find a way to do this.
Is there a way already available to achieve this or it needs to be added
as an enhancement?
Kindly let me know.
Thanks in advance,
Shashi
Mike Wilson wrote:
Hi Shashi,
Just as Jose says, incremental config/deconfig at runtime is
not supported currently in DWR. I do think though that this
is interesting for the future, especially as OSGI is gaining
ground in the Java EE area. I've added this feature request
to track this, and I hope we can at least offer an API you
can use to solve some of this in the next version of DWR
(after 3.0). We will need to do some refactorings for GAE
and I'm thinking OSGI might be possible to consider at the
same time.
From mailing list thread "How To: deconfigure the registered beans?":
Shashi wrote:
We are using DWR in OSGi environment wherein we have multiple bundles containing dwr configurations and getting loaded dynamically in the Container object available with a web bundle.
This is working like charm.
Currently I am looking to deconfigure the services registered in the container at runtime if a bundle goes down. Using the DwrXmlConfigurator and Container API I can't find a way to do this.
Is there a way already available to achieve this or it needs to be added
as an enhancement?
Kindly let me know.
Thanks in advance,
Shashi
Mike Wilson wrote:
Hi Shashi,
Just as Jose says, incremental config/deconfig at runtime is
not supported currently in DWR. I do think though that this
is interesting for the future, especially as OSGI is gaining
ground in the Java EE area. I've added this feature request
to track this, and I hope we can at least offer an API you
can use to solve some of this in the next version of DWR
(after 3.0). We will need to do some refactorings for GAE
and I'm thinking OSGI might be possible to consider at the
same time.