Pax Web - 1.0.0
1.0.0
February 4th, 2011
This release is a Major Release
Bug
PAXWEB-98 - JasperClassLoader causes JSF FactoryFinder to fail during request dispatch
PAXWEB-108 - Registering a servlet at "/" causes incorrect setting of servlet path and path info on request
PAXWEB-209 - War extender default context should be named "default"
PAXWEB-220 - ServletContext registration throws Exception for DefaultServlet
PAXWEB-222 - WarDeployer should append official Web-ContextPath to the manifest
PAXWEB-225 - JSP pages with same name/path in different contexts will be shared
PAXWEB-230 - Webroot branch is missing a commit; integration of webroot is broken
PAXWEB-231 - ServletContext showing 404 when startup time of war is a bit longer
PAXWEB-233 - Resources ending in "/" cannot be loaded
PAXWEB-235 - ServletContext: osgi.web.contextpath needs to start with a "/"
PAXWEB-236 - pax-web-deployer: non versioned wars contain war in web-contextpath
PAXWEB-237 - pax-web-deployer: deployed war archive can not be deleted while server is running
Improvement
PAXWEB-114 - Use mime-util to determine mime types
PAXWEB-174 - Resources are sent without Last-Modified and no check is done for If-Modified-Since
PAXWEB-179 - Handle ServerControllerFactory dynamics
PAXWEB-216 - Send event admin events for web app lifecycle as described in the OSGi Web Application spec
PAXWEB-217 - Publish the ServletContext as described in the OSGi Web Application spec
PAXWEB-218 - Support for multiple apps on the same context path as described in the OSGi Web Application spec
PAXWEB-219 - Configuration through Felix-Webconsole should be possible
PAXWEB-221 - Dynamic adaption of Manifest
PAXWEB-223 - Make sure only one bundle per Web-ContextPath is deployed
PAXWEB-224 - Add possibility to specify root directory in a bundle with WAR contents
PAXWEB-226 - Make the configuration parameters for JSPs changeable
PAXWEB-227 - Default configuration should only be configured in one place
PAXWEB-229 - The HTTP TRACE method needs to be disabled to avoid Cross-Site Tracing (XST) vulnerability
PAXWEB-234 - When deploying a web application with pax-logging installed, the web app should import pax-logging packages (with maybe a configurable flag to disable this behavior)
PAXWEB-239 - upgrade to pax-swissbox 1.3.1
New Feature
PAXWEB-228 - Implement a listener with replay events
PAXWEB-238 - WAB as Fragment
Task
PAXWEB-232 - Release Pax-Web 1.0.0