Today I contacted the maintainer of the BadResource.java file about the bug I found. Only a few minutes later my inbox contained an answer. He told me that he read about the bug on the mailinglist and that he has not responded because of lack of time. He will perhaps work on it later this week. If you need a fix by now you may simply remove the toString() method from BadResource.java or you may download my patched jar.

I was working on an ActionForm which has the property password. When I was testing the JSP view I wondered why the field always was filled although I never called the corresponding setter in the action. “Damn”, I thought. “Where does this stupid value come from?” I had no clue. Then suddenly a light flashed through my mind: Mozilla has a nice feature called “auto fill forms” ... oh my =)

If you want to keep your JSP compilation results between server restarts you have to tell Jetty where to put the results. Otherwise Jetty will use a different directory on each restart. The simplest way is to add an init-parameter in webdefault.xml: [code] jsp org.apache.jasper.servlet.JspServlet scratchdir /tmp/jetty 0 [/code]

If you try to redeply a webapp via jmx-console in JBoss/Jetty you may get the following error:

java.io.FileNotFoundException: C:\java\jboss-3.2.1\...\jbossweb-jetty.sar\.\webdefault.xml 
is alias of C:\java\jboss-3.2.1\...\jbossweb-jetty.sar\webdefault.xml
...

After digging into the sources I possibly found the bug in the toString() method of BadResource.java because the toString() method appends additional information to the original URL. The toString() method, however, is used by WebApplicationContext as the path to webdefault.xml.
I have already posted a mail on the jetty-discuss mailinglist. I will keep you informed about ...

Talking to the database on each request is not necessary because the content of my weblog does not change very often (for now =) ). So I like the idea of using a cache. Whenever I add a new entry I could send a notification to the cache and the cache would be flushed. So far so good. The tricky thing now is that I am using Tiles and putting a cache taglib into the tile would have no effect because the correspondig Action, which talks to the database, would still get called. Therefore I need a cache logic before the Action ...