One option is to get a stock jetty download, and copy across our configuration
& application files - then you'll have all their scripts.
Alternatively here's a quick and dirty start script you could use to pull the
info from wrapper.conf which should keep working with new versions:
#!/bin/sh
set -e
(
cd `dirname $0`/..
if [ -z "$CONTINUUM_BASE" ]; then
CONTINUUM_BASE=.
fi
REPO_DIR=lib
CP=`cat conf/wrapper.conf | grep ^wrapper.java.classpath.[0-9]*= | grep -v
'.pom$' | sed 's/wrapper.java.classpath.[0-9]*=//' | sed
"s#%REPO_DIR%#$REPO_DIR#" | tr '\n' ':' | sed 's/:$//'`
ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed
's/wrapper.app.parameter.[0-9]*=//' | tr '\n' ' '`
JVM_ARGS=`cat conf/wrapper.conf | egrep ^wrapper.java.additional.[0-9]*= |
sed 's/wrapper.java.additional.[0-9]*=//' | sed
"s#%CONTINUUM_BASE%#$CONTINUUM_BASE#" | tr '\n' ' '`
JVM_MINMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.minmemory= | sed
's/wrapper.java.minmemory=//'`
if [ ! -z "$JVM_MINMEM_ARG" ]; then
JVM_ARGS="-Xms${JVM_MINMEM_ARG}m $JVM_ARGS"
fi
JVM_MAXMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.maxmemory= | sed
's/wrapper.java.maxmemory=//'`
if [ ! -z "$JVM_MAXMEM_ARG" ]; then
JVM_ARGS="-Xmx${JVM_MAXMEM_ARG}m $JVM_ARGS"
fi
java -cp $CP $JVM_ARGS $ARGS
)
On 30/11/2012, at 12:41 AM, "Leitch, Oblio" <[email protected]> wrote:
> Yeah, that sounds like a plan. I see that Jetty's included in the
> stand-alone version. How would I get that started?
>
> -----Original Message-----
> From: Brett Porter [mailto:[email protected]] On Behalf Of Brett Porter
> Sent: Wednesday, November 28, 2012 7:00 PM
> To: [email protected]
> Subject: Re: new user question
>
> Another option is to deploy the WAR into your application server of choice.
> Perhaps we should have a wrapper-less startup script to do that with Jetty...
>
> - Brett
--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
