If you're looking for a fast and easy way to run your webapp, without needing to install and administer a Jetty distro, then look no further, the Jetty Runner is here! The idea of the Jetty Runner is extremely simple - run a webapp from the command line using a single jar and as much default configuration as possible:

  java -jar jetty-runner.jar my.war

Voila! Jetty will start on port 8080 and deploy the my.war webapp.

Read more...

In one of those cosmic coincidences, no sooner do I blog about OSGi and J2EE containers, but Glassfish announces that they are moving to OSGi.

Read more...

Read more...

The JSR-316 group - the JavaEE expert group - has suggested the idea of "profiles" to formally provide the option of slimmed-down app servers. There are various options being mooted for a Web Profile, but all of them contain JSP and related technologies as mandatory. I argue that the time for JSP as a mandated presentation technology has past and a Web Profile should simply consist of the servlet specification. In fact, I'm doubtful of the profile solution, and see much more value in a flexible container that allows you to plug in the implementations of the standard APIs as your needs dictate.

Read more...

Jetty is now serving web pages to the Android browser. The web pages show various types of information stored on the device, such as the current call log, the system settings, and the contact list.

Read more...

I've recently been working on porting Jetty to Google's mobile platform called Android.

It's early days still, but I've succeeded in running a minimal setup with a connector (I've tested both bio and nio connectors) and a simple Handler. If you'd like to take a look, then check out the code from the i-jetty project and build it (you'll need to execute the ant build script and then use Android's packaging tool or the Eclipse plugin).

Once you've built and deployed the i-jetty package to the emulator,  find the "Manage Jetty" application, and select the "Start Jetty" button. Then you'll be able to select the Browser application and surf to http://127.0.0.1:8080 and hit the demo "Hello" Handler.

For the moment I've had to do a teeny hack to the servlet api classes, due to this bug in Android, but hopefully that will be fixed soon and I can revert the temporary patches.

Much work remains to be done, but I thought I'd give everyone early warning that this work was going on. Who knows, it might inspire someone to use Jetty to win the Android developer challenge?!

I just came across a very cool use of Jetty.

The folks at IBM alphaWorks have come up with an Eclipse plugin that translates your Eclipse UI into XUL and vice-versa so that you can effectively use your Eclipse from your (Mozilla-based) web browser! Jetty is the servlet engine providing the browser-to-Eclipse linkage.

Go and check it out at: www.alphaworks.ibm.com/tech/eclifox

One slight problem is that the first release of the plugin will only work on Windows platforms, however they're working on an update that should be platform independent.

The plugin currently requires you to download the Jetty jars separately, however as Eclipse 3.3 and onwards ships with an internally available Jetty, the alphaWorks guys may well be able to hook into that in a future release, streamlining the installation process and reducing duplication.

Version 1.0.1 of the Jetty Plugin for Eclipse is available from:

www.webtide.com/eclipse/

This minor release fixes a problem whereby the automatic redeploy of a Dynamic Webapp project by the Eclipse environment did not trigger Jetty to redeploy.

We've been collaborating with the guys from Terracotta to create a new clustering solution for Jetty HTTP sessions.

Make a note to drop by the Terracotta stand at Java One (booth #828) and see a demo of it in action!

Read more...

Jetty has a sexy new plugin for Ant that has the same features as the Maven plugin. So if you didn't want to move from Ant to Maven, but you still want fast webapp development, now you can have it!

Read more...