Re: [equinox-dev] jetty-http / jsp / problem with session-scoped beans after bundle update

2010-03-02 Thread Yuriy Malchenko
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 wrote: > On 3 Mar 2010, at 0

Re: [equinox-dev] jetty-http / jsp / problem with session-scoped beans after bundle update

2010-03-02 Thread Alex Blewitt
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 i

[equinox-dev] jetty-http / jsp / problem with session-scoped beans after bundle update

2010-03-02 Thread Yuriy Malchenko
Hi! I'm playing with Jetty based HTTP Service and Jasper. And here's the problem: if I declare a session-scoped bean and then update the bundle which provides its class, I eventually get the JSP exception with cause saying: "java.lang.ClassCastException: com.yurique.web.SomeBean cannot be cast to