Deploying grails webapp to Jetty – resolving a few issues…

gregs — Tue, 23 Mar 2010 13:39:03 +0000

So you have deployed your app and can access the start page of your grails app. If you are like me deploying your app to a Debian\Jetty type of configuration you might come across the following error:

PLAIN TEXT

CODE:

java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config

When trying to access a controller from the default start page. I traced this to a missing dependency in grails (I use SpringSource Tool Suite for development so that maybe the root cause). By opening and editing your /project/grails-app/conf/(default package)/BuildConfig.groovy, add the following under grails.project.dependency.resolution.

PLAIN TEXT

CODE:

grails.project.dependency.resolution = {
...
dependencies {
// specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes eg.
runtime "javax.servlet:jstl:1.1.2"
// runtime 'mysql:mysql-connector-java:5.1.5'
}
}

Build your war and re-deploy. Still getting an error?? I was. For jetty there was still an issue with calling the controller. After spending some time exploring, it looks like Jetty support was removed from Grails 1.2. I stumbled across a post mentioning installing the grails Jetty plugin with:

PLAIN TEXT

CODE:

. grails install-plugin jetty

After running this, and re-building my war file and re-deploying it one final time, bingo it all worked.

Deploying grails app to Jetty

gregs — Sat, 20 Mar 2010 13:35:59 +0000

Short and sweet, step by step guide for creating a grails war and deploying it to your Jetty server (includes apache2 proxy steps)

grails war (your app), in this case epic.war
Copy to server
PLAIN TEXT
CODE:
1. scp epic.war user@server:/location
On Debian the location for jetty webapps is: /var/lib/jetty/webapps
Copy from upload location to the above folder (I used sudo)
Change permissions:
PLAIN TEXT
CODE:
1. sudo chown jetty:adm epic-0-0.1.war
created a *.xml context file in /etc/jetty/contexts, with something like this [note case is important!!]:
PLAIN TEXT
CODE:
1. "1.0" encoding="ISO-8859-1"?>
2. "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
3. "org.mortbay.jetty.webapp.WebAppContext">
4. "contextPath">/epic
5. "war">"jetty.home" default="."/>/webapps/epic-0-0.1.war
restart jetty :
PLAIN TEXT
CODE:
1. sudo /etc/init.d/jetty restart
(try stop/start as well)
test with :
PLAIN TEXT
CODE:
1. lynx http://localhost:8080/epic/
Nice but I'd like http://localhost/epic/ so enable mod_proxy in apache if you haven't already :
PLAIN TEXT
CODE:
1. a2enmod proxy
edit /etc/apache2/mods-enabled/proxy.load and if not present add at end:
PLAIN TEXT
CODE:
1. LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
edit your virtualhost conf file I am using 000-default and add:
PLAIN TEXT
CODE:
1. ProxyRequests Off
3. Order deny,allow
4. Allow from all
6. ProxyPass /epic http://localhost:8080/epic
7. ProxyPassReverse /epic http://localhost:8080/epic
8. ProxyPreserveHost On
restart apache :
PLAIN TEXT
CODE:
1. sudo /etc/init.d/apache2 restart
now you can
PLAIN TEXT
CODE:
1. lynx http://localhost/epic/

Update: I had omitted the ProxyPreserveHost On from the Apache configuration, which resulted in css, images and external javascripts not loading. It also caused an issue with accessing controllers.

Sources:

gregs » grails

Deploying grails webapp to Jetty – resolving a few issues…

Deploying grails app to Jetty