You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2006/08/10 01:35:24 UTC
testing forrest-0.8 as WAR in Jetty and Tomcat
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.
-David
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
...
>>>>> Would developers please try to use the current forrest
>>>>> trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
We need more testing.
...
>>>>> 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 Gav.
...
>>>> I will test it shortly on a dispatcher site.
>>> How did you go?
>> Thanks for the reminder, I just tried it now on a dispatcher site.
...
> And may relate this issue now to
> http://issues.apache.org/jira/browse/FOR-932
Dispatcher is in the whiteboard and so it does not matter if it does not
work in a deployed 0.8 war. As long as it works in the internal Jetty
and works for generating the static site (which it does) then we are goo
to go for 0.8.
I'll link this thread to the above issue and schedule that issue for 0.9.
Ross
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Thursday, 22 March 2007 6:51 PM
> To: dev@forrest.apache.org
> Subject: RE: testing forrest-0.8 as WAR in Jetty and Tomcat
>
>
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Thursday, 22 March 2007 3:11 PM
> > To: dev@forrest.apache.org
> > Subject: Re: testing forrest-0.8 as WAR in Jetty and Tomcat
> >
> > 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=70f6a0e1d75ac913d8b
> > 31
> > > 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?
>
> Thanks for the reminder, I just tried it now on a dispatcher site.
>
> I get :-
>
> Message: null
>
> Description: No details available.
>
> Sender: org.apache.cocoon.servlet.CocoonServlet
>
> Source: Cocoon Servlet
>
> Request URI
>
> index.html
>
> cause
>
> Could not resolve locationmap location.
>
> request-uri
>
> /my-project/index.html
>
>
> This happens for all .html files.
> All .xml files display fine.
>
> Gav...
And may relate this issue now to
http://issues.apache.org/jira/browse/FOR-932
Gav...
>
> >
> > -David
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date:
> 3/14/2007
> > 3:38 PM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
> 3:38 PM
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 22 March 2007 3:11 PM
> To: dev@forrest.apache.org
> Subject: Re: testing forrest-0.8 as WAR in Jetty and Tomcat
>
> 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=70f6a0e1d75ac913d8b
> 31
> > 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?
Thanks for the reminder, I just tried it now on a dispatcher site.
I get :-
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
index.html
cause
Could not resolve locationmap location.
request-uri
/my-project/index.html
This happens for all .html files.
All .xml files display fine.
Gav...
>
> -David
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
> 3:38 PM
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
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
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
Ray Mendonsa wrote:
> Ahhh. But then I stumbled upon this thread:
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113448256225368&w=2
Yes, see http://issues.apache.org/jira/browse/FOR-735
Thanks for finding that patch which disappeared in the
mail archive. I linked it to the jira issue.
> So now I know the plugins are deployed in war target only. I confirmed that
> feeder *was* deploying OK if I used war target. In my setup (Forrest cmd
> line on WinXp/Java 1.5.0_06, war running on FC2 Linux/Java 1.5.0_09/Tomcat
> 5.0.30)
Thanks for testing the 'forrest war'.
-David
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ray Mendonsa <ra...@linklord.com>.
Ahhh. But then I stumbled upon this thread:
http://marc.theaimsgroup.com/?l=forrest-dev&m=113448256225368&w=2
So now I know the plugins are deployed in war target only. I confirmed that
feeder *was* deploying OK if I used war target. In my setup (Forrest cmd
line on WinXp/Java 1.5.0_06, war running on FC2 Linux/Java 1.5.0_09/Tomcat
5.0.30)
Thanks,
Ray
-----Original Message-----
From: Ray Mendonsa [mailto:ray@linklord.com]
Sent: Thursday, November 09, 2006 9:56 PM
To: dev@forrest.apache.org
Subject: RE: testing forrest-0.8 as WAR in Jetty and Tomcat
wrt plugin deployment, I did confirm that the feeder plugin was not deployed
for me with the current 0.80-dev code with 'forrest webapp' run under Tomcat
5.0.30 on FC2 Linux under Java 1.5.0_09. Feeder plugin was working OK with
'forrest run'. Note 'forrest webapp' was run on Windows with 1.5.0_06 JDK
for this test.
There's an error reading
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml . There's /build/plugins/ folder in the output of 'forrest
webapp'.
I will look into it myself, but it will take me a while because I'm a
Forrest n00b and don't know the correct behaviors with certainty.
Ray
====
<snip>
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ray Mendonsa <ra...@linklord.com>.
wrt plugin deployment, I did confirm that the feeder plugin was not deployed
for me with the current 0.80-dev code with 'forrest webapp' run under Tomcat
5.0.30 on FC2 Linux under Java 1.5.0_09. Feeder plugin was working OK with
'forrest run'. Note 'forrest webapp' was run on Windows with 1.5.0_06 JDK
for this test.
There's an error reading
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml . There's /build/plugins/ folder in the output of 'forrest
webapp'.
I will look into it myself, but it will take me a while because I'm a
Forrest n00b and don't know the correct behaviors with certainty.
Ray
====
ERROR (2006-11-09) 21:32.56:820 [core.modules.mapper.lm] (/)
TP-Processor3/SelectNode: Ignoring locationmap config exception: Unable to
build LocationMap.
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
build LocationMap.
at
org.apache.forrest.locationmap.lm.MountNode.loadConfiguration(MountNode.java
:129)
at
org.apache.forrest.locationmap.lm.MountNode.getLocationMap(MountNode.java:87
)
at
org.apache.forrest.locationmap.lm.MountNode.locate(MountNode.java:157)
at
org.apache.forrest.locationmap.lm.SelectNode.locate(SelectNode.java:110)
at
org.apache.forrest.locationmap.lm.LocatorNode.locate(LocatorNode.java:122)
at
org.apache.forrest.locationmap.lm.LocationMap.locate(LocationMap.java:276)
at
org.apache.forrest.locationmap.lm.MountNode.locate(MountNode.java:157)
at
org.apache.forrest.locationmap.lm.SelectNode.locate(SelectNode.java:110)
at
org.apache.forrest.locationmap.lm.LocatorNode.locate(LocatorNode.java:122)
at
org.apache.forrest.locationmap.lm.LocationMap.locate(LocationMap.java:276)
at
org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapMod
ule.java:181)
at
org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolve
r.processModule(PreparedVariableResolver.java:246)
at
org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolve
r.resolve(PreparedVariableResolver.java:197)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectN
ode.java:77)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:77)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:155)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:77)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:292)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:223)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:289)
at org.apache.cocoon.Cocoon.process(Cocoon.java:557)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:364)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
Valve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.excalibur.source.SourceNotFoundException:
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml doesn't exist.
at
org.apache.excalibur.source.impl.FileSource.getInputStream(FileSource.java:1
50)
at
org.apache.forrest.locationmap.lm.MountNode.loadConfiguration(MountNode.java
:125)
... 49 more
Caused by: java.io.FileNotFoundException:
<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/locationm
ap.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at
org.apache.excalibur.source.impl.FileSource.getInputStream(FileSource.java:1
46)
... 50 more
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
On Thu, Aug 10, 2006 David Crossley wrote:
>
> 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.
Please, pretty please. Reports of success are good too.
We especially need to know that plugin deployment works properly.
The "seed-sample" site only includes the PDF plugin.
It would also be good to hear that Dispatcher works properly
in webapp mode.
If there are any out-of-the-ordinary configuration,
then please say. One of us can make a doc about
deployment issues for various situations.
-David
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 10 August 2006 7:35 AM
> To: dev@forrest.apache.org
> Subject: testing forrest-0.8 as WAR in Jetty and Tomcat
>
> 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. 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?
I will test it shortly on a dispatcher site.
Gav...