This post originated from an RSS feed registered with Java Buzz by Simon Brown. Original Post: Running Pebble on Resin 3.0.x Feed Title: Simon Brown's weblog Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java Feed Description: My thoughts on Java, software development and technology. Latest Java Buzz Posts Latest Java Buzz Posts by Simon Brown Latest Posts From Simon Brown's weblog

Apologies in advance for yet another "Running Pebble on app server X" post but a JIRA issue popped up today outlining a problem with Pebble on the latest version(s) of Resin. Having never used Resin 3.0.x I didn't have a clue how to deploy. Hopefully these instructions will help somebody, regardless of the webapp that they are trying to deploy.

Essentially, deploying a webapp on Resin 3.0.x is the same as deploying to Resin 2.1.x. Well, semantically the same but syntactically different.

1. Grab Resin from here and extract to a directory of your choice.
2. Grab Pebble from here and extract to a directory of your choice. As with Tomcat, you can either extract it underneath the $RESIN_HOME/webapps directory, or anywhere on your disk.
3. Assuming that you've extracted Pebble somewhere other than the webapps directory, open up the $RESIN_HOME/conf/resin.conf file and insert the following XML before the closing host tag, changing the id and document-directory attributes as necessary. In addition to this, you can set up the users that you need for your blog. In the example below I have a single user that is both a blog-owner and blog-contributor.

   <web-app id='blog'
     document-directory='/Users/simon/sandbox/pebble/pebble-web'>
     <authenticator>
       <type>com.caucho.server.security.XmlAuthenticator</type>
       <init>
         <user>simon:password:blog-owner,blog-contributor</user>
         <password-digest>none</password-digest>
       </init>
     </authenticator>
   </web-app>
   

If you do try to run the current version of Pebble (1.4) on Resin 3.0.x then it falls over saying that pages can't be found. After some digging around I've found that this is because Resin doesn't seem to like the following code where the value of an attribute is specified using Java code.

    <jsp:include page='<%= request.getParameter("content")%>' />

    <% 
��    String content = request.getParameter("content"); 
    %> 
    <jsp:include page="<%= content %>" />