launcher/app: Restarting the OPS4J Pax Server fails
---------------------------------------------------
Key: SLING-531
URL: https://issues.apache.org/jira/browse/SLING-531
Project: Sling
Issue Type: Improvement
Components: Launchpad Launcher
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: 2.0.1
When the OPS4J Pax Server which is included in the Standalone launcher to
implement the OSGi HttpService is restarted, no new servlet registrations work
any more.
The reason for this problem is linkage errors between the OSGi HttpService and
the Servlet API classes: The tricky thing is, that in the standalone launcher
the HttpService interfaces are exported by the system bundle, while the Servlet
API classes are exported by the Pax Server bundle. Now, the HttpService
interfaces refer to Servlet API interfaces and when the Pax Server bundle is
started the first thime, these HttpService interfaces seem to be linked with
the Servlet API classes of the Pax Server bundle.
If the Pax Server bundle is restarted, the HttpService interfaces are still
linked with the old classes, while the Pax Server is now using the new Servlet
API classes. Now, when the Pax Server uses the HttpService a linkage error
occurrs because the class instances of the Servlet API classes are not the same
for the HttpService interface and the Pax Server....
The fix to this delicate issue, is to export the Servlet API classes from the
standalone launcher together with the HttpService API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
