Thirteenth newsletter - we're not superstitious.  What's new this week?  Updates to layer0, visualizer, http transport.  First beta release of a NetKernel servlet solution.

Repository Updates

layer-0: INKFRequestReadOnly.getIssueableClone() was updated so that sticky headers are preserved on the cloned request.

visualizer: Fixed so that if the primary argument is null, it doesn't throw NPE either when viewing or saving the trace.

http-server:  An update was made to the HTTPBridge so that it attempts to interpret encoding of the text fields in mixed text and file multipart forms.  If encoding is not set, which seems to be common with several browsers, then it defaults to UTF-8.

NetKernel Servlet - Beta 1

The Servlet embedded version of NetKernel creates and boots an instance of NetKernel within a JEE Servlet container allowing Servlet based applications to utilize the flexibility, caching and other features of NetKernel within and alongside new and existing more traditional applications.

Download it here...

http://resources.1060research.com/aux/nkse/4/servlet/beta-1/netkernel-servlet-beta-1.zip

The solution is self-contained and includes a complete NKSE system ready to go within a servlet environment.

There are three files in this distribution, netkernelservlet.jar, web.jar and timeservice.war. The timeservice.war file is a complete ready-to-use web application which implements a RESTful time web service.

The netkernelservlet.jar file contains the NetKernel Servlet. This is a traditional servlet that can be installed in the WEB-INF/lib/ directory of a web application and configured in the web.xml

A detailed installation and usage guide is provided here...

http://resources.1060research.com/aux/nkse/4/servlet/beta-1/servlet-documentation.pdf

We have tested in Jetty, Tomcat 6 and JBoss all on OS X. Some testing has been done on Ubuntu and Windows, but this is not complete. We would appreciate if you could test in as many containers as possible and provide us with reports.

(If you found this content via a web search, you might want to know that NetKernel Standard Edition is a complete standalone solution with its own HTTP transports etc etc.  It doesn't require a Servlet container and  is very efficient on system resources.  It can also be deployed as an embedded POJO inside any Java system).

Since sending the newsletter on Friday we found that the Jetty HTTP server update causes a transient side effect during its update-install. Because the http-client module is removed and reinstalled its classloader is replaced.  However apposite uses a session cookie to maintain state - it therefore was linked with an instance of the old javax.servlet.Cookie class - but after install the classloader for the Cookies arriving from HTTP has changed.  Java can't cope with this situation and so throws a classloader exception. Basically, to cut this story short, updating HTTP is going to require that you do a reboot... http://localhost:1060/tools/reboot (Only apposite is effected by this transient prior to reboot, so this link works even if you are seeing the exception). Sorry about this, its unfortunate - we're going to have to figure out a way for the session prototype to detect the http server space change and cascade the change to the space hosting the session.   That or alter the session space to use reflection on the Cookie class so that it gets around Java. Hope this isn't too inconvenient.

The 1060 Team