something else to consider - where this gets even hairier :) user accesses a page that has a component from bundle A, the page is serialized. admin upgrades bundle A which has a new version of the component - that is not compatible serialization-wise user click back and the page needs to be serialized - error
what is needed here i some way to veto a bundle/version removal until all web sessions that access components in those bundles have timed out. this is not really wicket-specific, more web specific as web apps can stick objects into http session... -igor On Thu, Jun 23, 2011 at 4:30 PM, Brian Topping <[email protected]> wrote: > > On Jun 23, 2011, at 10:11 AM, Harald Wellmann wrote: > >>> what is really needed here is someone taking the time to build a >>> generic serialization mechanism for osgi. wicket's serialization is >>> pluggable so it can be hooked into that. >>> >> >> I'll take a look at the patches, play around with the code and find out if >> I'm one the wrong track or not... If I end up with anything interesting >> enough, I'll get back or attach another patch. > > I'm also taking a look at it. > --------------------------------------------------------------------- > 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]
