Alex, thanks for a quick response.
I guess I'll just be keeping this in mind as a feature. Dropping all sessions indeed sounds unreasonable (especially having other bundles with own resources and sessions). --- Yurique On Wed, Mar 3, 2010 at 3:24 AM, Alex Blewitt <[email protected]> wrote: > On 3 Mar 2010, at 00:51, Yuriy Malchenko wrote: > >> Or maybe I should take the needed classes (session/application scoped) >> to a separate bundle which will not be needed to update frequently? >> But anyway sometimes it might, so it's not a good solution. > > It's generally a good idea to separate out interfaces/classes which are going > to be exposed to the end user and make them available in a separate bundle, > whilst having your logic/program in a different bundle. Then you can throw > away the program and reinstantiate it after update, but keep your data > objects/interfaces the same. > > Note that applies to a number of other cases where the implementation must be > bounced but whilst maintaining the same interface classes; it's not unique to > servlets or JSPs, though of course, you notice these in situations like this. > > The other approach is to drop all sessions when you reload the code, which > doesn't sound like a sensible solution. > > Alex_______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev > _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
