Migrating to Pebble 2.0 on Jetty

An article by Glen    No Comments

I’ve cut over from Pebble 1.9 to 2.0 RC1 without too many issues. But for those of you attempting this down the track, here are a few of my hurts to learn from…

First it would not display any of my previous 1.9 entries. Whenever I attempted to reindex it would dump out FATAL errors to the logs. I finally wound up logging on the Pebble DAO stuff and saw:

Loading /data/pebble/blogs/glen/2004/03/13/1079209312000.xml
org.xml.sax.SAXParseException: Premature end of file.

Turns out some of my old pebble blog entries must have died with a 0 length file (there was typically a .bak file right next door which I could just rename). Once that was sorted, a full reindex and they all came back. Phew!

The next hurdle was getting RSS feeds working again. Due to a bug in Jetty that Greg discussed on the mailing list, .xml files weren’t being processed correctly. I ended up having to add the following entries to Pebble’s web.xml:

<servlet>
    <servlet-name>jspxml</servlet-name>
    <servlet-class>org.apache.jasper.servlet.JspServlet </servlet-class>
  </servlet>

  <servlet-mapping>
        <servlet-name>jspxml</servlet-name>
        <url-pattern>*.xml</url-pattern>
  </servlet-mapping>

Pebble 2.0 looks really good. Simon’s made the move to a total Spring solution with this release, using Acegi for the security engine, so I’m keen to take a wander through the source – been meaning to learn Acegi for ages.

Big props to Simon and the guys for a great new release!