Pinned topic Does OSGi update affect the current app session?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
In WAS V8, OSGi bundle can be pluged in and out, which doesn't need to be restarted. Will this step affect the current app session? How can we insure the access from user will not be interrupt when updating a bundle.
Updated on 2011-08-09T13:25:44Z at 2011-08-09T13:25:44Z by MarkN
MarkN 110000BE39124 Posts
Re: Does OSGi update affect the current app session?2011-08-09T13:25:44ZThis is the accepted answer. This is the accepted answer.Hello,
Will this step affect the current app session? How can we insure the access from user will not be interrupt when updating a bundle.
First of all please have a look at this Infocenter topic. The "Results" section at the end includes a discussion of which updates will cause other bundles, or the entire application to be restarted, and which won't. User access to an OSGi web application will clearly be interrupted if the relevant Web Application Bundle is itself updated, or if it is caused to be restarted. To that extent, WABs should not import packages from other other bundles that themselves include application logic. Ideally, WABs should interact with other bundles via OSGi services whose interfaces are separated into an API bundle containing just those interface definitions. We also recommend that WABs use damped service references via the blueprint:comp namespace, so that end-users experience only short pauses, rather than broken requests, if a user request coincides with a bundle update. Please see this Infocenter topic for more information.