Ouch! That hurts. Please have mercy on those damned to DBCP hell.

I think I may have to ask for my money back. I downloaded 1.4b2 and tried it with both Resin 2.1 and Resin 3.0.6.

Under Resin 3.0.6 it blew up spectacularly with reams of JSP compilation errors. I didn't get to read them all, but a lot seemed to relate to SAX.

Under Resin 2.1 it initially seemed to work, but the problems were more subtle. None of the images on the front page appeared, despite seemingly innocuous relative URLs Worse than that, none of the actions work either. Looking closer, I see the problem: the generated page shoots itself in the foot with a hard-coded (and needless?)

<base href="http://localhost:8080/blog/" />

so in my port 80 installation of a war named "pebble" everything collapses.

Good job it's only a beta, hmm :)

I had a look through the code and, I must admit I can't actually see why you need the blog.url parameter at all.

generating the base href just seems to screw things up if its not right, and omitting it completely seems to make the app more flexible. Relative URLs always seem more robust that absolute ones to me.

On the off-chance that there is some situation where it might be needed, I guess you could allow it to be set in web.xml, but wouldn't a default empty value (implying don't generate the base href, and use request.getContextPath() if its needed elsewhere) make deploying pebble even easier?

Then, if you default blog.dir to the web app temp directory provided by the container, you could probably get a zero-config install (like I do with Friki) :)

A zero-config install would be wonderful, but it's not very easy. The blog.url property is there because I would like to be explicit about blog permalinks. This property used to be specified in the blog.properties file but I moved it. Also, there's some rather funky URL filtering that goes on in multi-user mode so the base href is necessary. I did try to get Pebble to automatically work out the base href and while it worked, it was a little flaky - particularly if you are running on a box with multiple identities (i.e. hostnames).

The blog.dir is also important and I certainly don't want blog data to be saved in the container temp directory, even just as a default - I'd rather force people to think about where they would like to install their blog upfront.

Although you do need to set this stuff up, it does making moving blogs from one server to another very easy, and likewise updating Pebble is also easy.

Thanks simon. I can see the "My weblog" page with the images but I cant login to configure the blog. When I deploy the log message is : 2004-02-13 13:54:20,413 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.3/server/default/deploy/pebble.war/ 2004-02-13 13:54:20,744 INFO [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] deploy, ctxPath=/pebble, warUrl=file:/C:/jboss-3.2.3/server/default/deploy/pebble.war/ 2004-02-13 13:54:22,006 INFO [org.jboss.web.localhost.Engine] SingleSignOnContextConfig[/pebble]: WARNING: Security role name some-nonexistent-role used in an <auth-constraint> without being defined in a <security-role> 2004-02-13 13:54:23,358 INFO [org.jboss.web.localhost.Engine] SingleSignOnContextConfig[/pebble]: Added certificates -> request attribute Valve 2004-02-13 13:54:23,368 INFO [org.jboss.web.localhost.Engine] SingleSignOnContextConfig[/pebble]: Configured an authenticator for method FORM 2004-02-13 13:54:23,458 WARN [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] Unable to invoke setDelegate on class loader:org.jboss.web.tomcat.tc4.WebCtxLoader$ENCLoader@15d45d9 2004-02-13 13:54:23,468 INFO [org.jboss.web.localhost.Engine] StandardManager[/pebble]: Seeding random number generator class java.security.SecureRandom 2004-02-13 13:54:23,468 INFO [org.jboss.web.localhost.Engine] StandardManager[/pebble]: Seeding of random number generator has been completed 2004-02-13 13:54:23,588 INFO [pebble.listener.PebbleContextListener] Starting Pebble 1.4-beta1 2004-02-13 13:54:23,588 INFO [pebble.listener.PebbleContextListener] blog.url is http://localhost:8080/pebble/ 2004-02-13 13:54:23,588 INFO [pebble.listener.PebbleContextListener] blog.dir is /Users/simon/sandbox/pebble/blog 2004-02-13 13:54:23,598 INFO [pebble.listener.PebbleContextListener] DAOFactory in use is pebble.blog.persistence.file.FileDAOFactory 2004-02-13 13:54:23,598 INFO [pebble.listener.PebbleContextListener] blog.owner is blog-owner 2004-02-13 13:54:23,598 INFO [pebble.listener.PebbleContextListener] blog.contributor is blog-contributor 2004-02-13 13:54:23,628 INFO [pebble.blog.BlogManager] Running in single user mode 2004-02-13 13:54:23,828 INFO [org.jboss.web.localhost.Engine] StandardWrapper[/pebble:default]: Loading container servlet default 2004-02-13 13:54:23,828 INFO [org.jboss.web.localhost.Engine] StandardWrapper[/pebble:invoker]: Loading container servlet invoker 2004-02-13 13:54:24,830 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss-3.2.3/server/default/deploy/pebble.war/

It worked. Thanks for your help!

I downloaded the code and has it working under jboss-3.2.2 except the time zone info is not right after I change it to US/Pacific. Any ideas?

Thanks Simon, I restarted the server and things seems to work fine. However there are several error messages in the server log that bothers me. 1. When I do a search, I got the following error: MAPPING configuration error for request URI /favicon.ico 2. When I deploy pebble, I got some security issues: WARNING: Security role name some-nonexistent-role used in an <auth-constraint> without being defined in a <security-role> Any ideas what may have happended? Thanks!

I thought that it might be! The security role stuff is fine - I set up a non-existent role that stops anybody accessing the resources that the role refers to. Basically, it's there to stop people calling those JSPs directly. :-)

Well it didn't take me five minutes but it was moderately simple once I worked out what was going on.

Initially I set up tomcat4 using apt-get and installed the pebble.war. This didn't work initially because of some security problems and t...