/
Pax Web - 0.8.0

Pax Web - 0.8.0

Oct 27, 2010
Unknown macro: {zone-template-instance}
Unknown macro: {zone-data}

0.8.0

Unknown macro: {zone-data}

October 27, 2010

Unknown macro: {zone-data}

This release highlights are:

  • Enable HTTPS support
  • Allow configuration of load-on-startup in web.xml
  • Use Jetty 7.2 (as bundled version)
  • Numerous fixes and improvements
Unknown macro: {zone-data}
  • Bug
    • PAXWEB-190 - Error generated when deploying a jar (which is a WAR) containing more than 1 xml file in WEB-INF folder (Number of xml's was not equal to 2. Was: 1)
    • PAXWEB-195 - JSTL core import tag failure
    • PAXWEB-196 - Security issues in WAR management
    • PAXWEB-199 - Cannot import org.apache.jasper.compiler, org.apache.jasper.el and org.apache.el
    • PAXWEB-201 - Can't configure session-timeout setting with web.xml
    • PAXWEB-206 - Web extender does not read the Web-ContextPath header defined in the Web applications chapter of the OSGi enterprise 4.2 release.
    • PAXWEB-207 - The Pax Web extender for Web Application Bundles does not appear to serve content from fragments
    • PAXWEB-208 - War extender only supports ".jsp" extension for JSPs
    • PAXWEB-211 - OSGi web apps should have their OSGI-INF folder protected
  • Improvement
    • PAXWEB-189 - org.ops4j.pax.web.service.internal.ConfigurationImpl logging statement does not show listening addresses it uses String[].toString()
    • PAXWEB-192 - Enable HTTPS support
    • PAXWEB-193 - Add a possibility to define a Jetty XML configuration using Config Manager (or system property)
    • PAXWEB-210 - Security Constraints for WebApplications
    • PAXWEB-212 - The web-deployer should also be able to handle exploded jars (jardir)
  • New Feature
    • PAXWEB-205 - Can't configure load-on-startup in web.xml
  • Task