Schlagwort-Archive: pax-web

Pax Web breaks the 200.000 downloads barrier

Pax Web breaks the 200.000 downloads barrier

just today I checked the latest download numbers from the central statistics for the pax-web project. It’s been good that I’ve been sitting already, cause a increase from 125.000 to more then 200.000 downloads, that’s quite impressive.

Thanks to all the people using Pax-Web, this number gives me faith in beeing on the right track with Pax-Web.

Bellow are just some graphics from the download statistics, as usual the three most important. All Artefacts downloaded (which is 200.000), all pax-web-jetty bundles (> 35.000) and all pax-web-jetty-bundles (the prebundled pax-web including jetty with around 4.000).

Just Annotation

Starting with version 2.0 of Pax-Web it’s possible to use Servlet 3.0 annotations for Servlets in a web application bundle (WAB). As defined in the Servlet spec it’s possible to have servlet definitions and configuration either in a web.xml or in the annotations of the Servlet. In this case the annotation of the servlet does override the configuration found in the web.xml. According to the servlet spec it’s even possible to skip the web.xml completely. That’s the part where Pax-Web 3.0 will kick in. Starting with version 3.0.0.M2 it’s possible to deploy a purely annotated WAB. It just needs a annotated Servlet

Bind certain Web-Applications to specific HttpConnectors

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.

    <Call name="addConnector">
      <Arg>
          <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
            <Set name="host"><Property name="jetty.host" /></Set>
            <Set name="port"><Property name="jetty.port" default="8282"/></Set>
            <Set name="maxIdleTime">300000</Set>
            <Set name="Acceptors">2</Set>
            <Set name="statsOn">false</Set>
            <Set name="confidentialPort">8443</Set>
            <Set name="name">jettyConn1</Set>
	    <Set name="lowResourcesConnections">20000</Set>
	    <Set name="lowResourcesMaxIdleTime">5000</Set>
          </New>
      </Arg>
    </Call>

Make sure you have a name configured for this connector. The sample uses jettyConn1 as name.

Pax Web 2.0.0

It’s released, at last.
This release did consume quite an amount of time.
I started to work on Pax Web 2.0.0 in July 2011, about the same time
we bought our new house with lots of renovation to be done.
77 Issues where resolved with 2.0.0 of Pax Web.
I’d say about 5k lines of Code where added in this time, at lease
that’s what git tries to tell me 🙂
Take a look at the image from Git hub for the Code Frequency at github.

Lot’s of improvements where made to Pax Web, Bugfixes, new features and so on.
To get a better picture take a look at http://team.ops4j.org/wiki/display/paxweb/Pax+Web+-+2.0.0