[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] jetty-http / jsp / problem with session-scoped beans after bundle update
- From: Yuriy Malchenko <jmalchenko@xxxxxxxxx>
- Date: Wed, 3 Mar 2010 03:40:55 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=IXDPpN9Xi7q6eMTXOwSlptHZx7kHWYvhhwhwOt6VMiO6P04Fu441inVSumUGMBfToP 2MpqDyRmkmT67qDcyM+eaAW3tmOE1hJUgTmySLEwE7WIidY1FGUg2iiy3TklMo/jBzQr t4C2NmXKft/6Jkb+3uad/qIh8hWTLr0fWkSqY=
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).
On Wed, Mar 3, 2010 at 3:24 AM, Alex Blewitt <alex.blewitt@xxxxxxxxx> 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.
> equinox-dev mailing list