Community
Participate
Working Groups
Build Identifier: 20100617-1415 We have made a number of modifications to the Equinox Server-side component. I've talked with Simon Kaegi in an email thread about the details. Below is a list of some of the changes we've made. - provide websession/servletcontext isolation to bundles - support for running in a clustered environment on tomcat / websphere / weblogic / netweaver - greater support for servlet apis such as listeners - configuration of servlets/filters using web.xml per bundle - ability to provide global configurations for all bundles - optimization of jsp engine by setting appropriate defaults - optimization of jsp classloader with precompiled jsps to only look in the current bundle for classes - numerous mechanisms for url management - security improvement such as not streaming back source files - ability to patch configuration in multiple files to simplify patching - using system properties to read in jars from a single locations in mulitple bundles to ensure classpath isolation at runtime but maintaining single copy of jars - ability to specify custom 404 pages - logging at startup time to catch errors - ensure redeployment of updated application works on numerous appserver by cleaning work dir - ability to read and get contents from files outside osgi container - support for running in development mode and production mode Reproducible: Always Steps to Reproduce: I have attached the changes we have made.
Created attachment 179771 [details] The attachment contains the changes we have made which I have discussed in the problem report.
Created attachment 189666 [details] Additional changes as of Feb 23, 2011 These are additional changes to the previously posted changes to the ServletBridge component by Taimur Javed
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
