Starting with Pax-Web 2.1 it’s possible to bind web applications to a specific http-connector. For this to work you need to configure an additional http connector through jetty.xml. The jetty.xml for pax-web uses a slightly different way of configuring connectors. Instead of setting a new Connector the jetty.xml is interpreted after the Jetty Server has already been configured. Therefore you need to add a connector, not create a new one.
<Set name="host"><Property name="jetty.host" /></Set>
<Set name="port"><Property name="jetty.port" default="8282"/></Set>
Make sure you have a name configured for this connector. The sample uses jettyConn1 as name.
This is a preview of
Bind certain Web-Applications to specific HttpConnectors
. Read the full post (170 words, estimated 41 secs reading time)
This article will try to give you a brief overview on what’s new in the soon to come Pax-Web 3.0.0. First of all, the most outstanding new feature will be the support for Tomcat as an alternative Container. Right now it supports basic HTTP Services, but this is being worked on.
Second there is a new support for binding Web-Applications to certain Http-Connectors aka Virtual-Hosts. More on this can be found soon on this blog. Find it here.
Third it’s now possible to deploy WABs without a web.xml. This requires „Servlet 3.0“ compliant Servlets within. A quick howto will also be available soon on this blog. Find it here
Now, that the year 2012 is over, it’s time to sum up the last year on what happened. Gather some statistics and a give an introduction of what is on the road-map for the next year.
What did happen in 2012
A quick overview of the timeline in 2012
The last release of Pax Web in December 2011 was 1.0.8 which was a bug-fix release which was very important for Pax Web, it’s been a good foundation for all others to come. In January Pax Web in version 1.1.2 was released this has been an important bug-fix release, It contained about 30 fixes.