forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Date Thu, 22 Mar 2007 06:10:42 GMT
On Dec 11 2006 Gav.... wrote:
> From: David Crossley
> > Sent: Thursday, 10 August 2006
> > 
> > Would developers please try to use the current forrest
> > trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
> > 
> > Do ...
> > cd my-new-directory
> > forrest seed-sample war
> > 
> > Then deploy the my-project.war to your servlet container.
> > 
> > Then try it on a site that uses your favourite plugins.
> > 
> > This is needed to progress towards the 0.8 release.
> > 
> > We need reports for various versions of Jetty and Tomcat,
> > so we need multiple developers to help with this testing.
> 
> You already have my success story for Tomcat 6.

Thanks. See https://issues.apache.org/jira/browse/FOR-765

> So I thought 
> I would try using Jetty.
> 
> 1. - I have downloaded Jetty 6.
> 2. - java -jar start.jar etc/jetty.xml etc/jetty.xml
> 3. - Localhost:8080 brings up jetty sample site ok
> 4. - Download Maven 2
> 5. - Build Jetty with Maven 2, Build failed error which 
>      I summised to be
> http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=70f6a0e1d75ac913d8b31
> fba76c1:YfiG?bug_id=4352234
> 
> ( 4 and 5, I was going to run 'mvn jetty:run' to use the plugin but this
> Didn't work out.)
> 
> So in the end, using Full Jetty version 6.
> 
> 1. 'forrest war' on a seed-sample site.
> 2. Copied WAR file to Jettys /webapp/ directory. (rather than configure
> files)
> 3. java -jar start.jar etc/jetty.xml etc/jetty.xml
> 4. http://localhost:8080/my-project/
> 
> All works fine.
> 
> So maybe you are using the forrest jetty or some other way of doing it.
> Could you guide me through your scenario so I can try it?

Yes i meant using a full separate version of Jetty, not Forrest's
packaged one which is a cut-down of an old Jetty.

I followed your method today, and yes it works for me
with Java 5 and Jetty 6.

I had been trying with a local configuration and starting
Jetty with a shell-script. Perhaps that config was not correct.
Anyway just using default config and 'java -jar start.jar etc/jetty.xml'
it works.

However doing the same with Java 1.4.2 is not working.
It gives the error described in FOR-765.

> I will test it shortly on a dispatcher site.

How did you go?

-David

Mime
View raw message