You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Bert Van Kets <be...@apache.org> on 2002/11/09 13:19:52 UTC
forrest war
Hi guys,
I am trying to get in pace with the recent Forrest development. Man, has
this project moved since I created the skin.
I did a completely fresh checkout and tried the "Forrest seed", "Forrest"
and Forrest war" commands and have two problems.
1. The dynamic links in the generated site are not correct. The selected
menu item is not yellow, like it should be. Haven't had the time to check
out why yet.
2. After building the war file and starting it up in Tomcat I get an
Internal Server error. Here's the stack trace:
javax.servlet.ServletException: Servlet.init() for servlet Cocoon2 threw
exception
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:871)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:615)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2344)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:462)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106)
at java.lang.Thread.run(Thread.java:484)
root cause
java.lang.NoClassDefFoundError: javax/xml/transform/URIResolver
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1534)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:852)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1273)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1156)
at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.configure(ExcaliburComponentManager.java:435)
at org.apache.cocoon.Cocoon.configure(Cocoon.java:418)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:284)
at
org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1255)
at
org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:454)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:615)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2344)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:462)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106)
at java.lang.Thread.run(Thread.java:484)
Anyway, big applause specially to Jeff who has been doing a great job lately!
Bert
Re: css skins (Re: forrest war)
Posted by Bert Van Kets <be...@vankets.com>.
At 02:11 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 03:25:14PM +0100, Bert Van Kets wrote:
>...
> > I'm building the new skin using as much CSS as possible. IMHO This
> will be
> > the most beautiful and fastest skin ever built for Forrest. :-)
>
>Wohoo :)
Don't get too overexcited. This skin is for my personal site and is all
about Radio Controlled gliders, planes and helicopters.
Sorry man,
Bert
>FYI, over the next few days I'm planning on factoring stuff out of the
>forrest-site and avalon-tigris skins into a common repository, and
>generally fixing the stylesheets. The aim is to make skin maintenance
>less of a PITA. If you're in the early stages of design this won't
>affect you.. hopefully the XSLTs will be less horrible by the time you
>get to them.
>
>Rounding up recent CSS skin stuff:
>
>Robert Koberg:
>
> "If you all want, we can use the livestoryboard.com site as a base for
> a forrest skin. We have put ALOT of work into the layout/css. The site
> can look extremely different by simply changing the CSS."
> <AD...@koberg.com>
>
>
>The tigris skin mentioned earlier:
>
>http://style.tigris.org/nonav/dev/docs/sampler_inst.html
>
>
>And in case anyone forgets, the portal-like Forrest front page in CVS,
>using lots of CSS:
>
>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/layout/xml.apache.org/home.html?rev=1.3
>
>
>--Jeff
>
>
> > Bert
> >
Re: css skins (Re: forrest war)
Posted by Bert Van Kets <be...@vankets.com>.
I agree with all this. CSS can make the skin easier to maintain and make
the site a LOT faster as the styling (CSS file) is cached by the browser.
One thing I personally will never accept is that we break backward
compatibility with older browsers. Please don't start a new thread on this
one, we have spent enough bandwidth on this already. We have to wait until
some definite stats are available to be absolutely sure version
compatibility can be upgraded to version 5.
Bert
At 02:11 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 03:25:14PM +0100, Bert Van Kets wrote:
>...
> > I'm building the new skin using as much CSS as possible. IMHO This
> will be
> > the most beautiful and fastest skin ever built for Forrest. :-)
>
>Wohoo :)
>
>FYI, over the next few days I'm planning on factoring stuff out of the
>forrest-site and avalon-tigris skins into a common repository, and
>generally fixing the stylesheets. The aim is to make skin maintenance
>less of a PITA. If you're in the early stages of design this won't
>affect you.. hopefully the XSLTs will be less horrible by the time you
>get to them.
>
>Rounding up recent CSS skin stuff:
>
>Robert Koberg:
>
> "If you all want, we can use the livestoryboard.com site as a base for
> a forrest skin. We have put ALOT of work into the layout/css. The site
> can look extremely different by simply changing the CSS."
> <AD...@koberg.com>
>
>
>The tigris skin mentioned earlier:
>
>http://style.tigris.org/nonav/dev/docs/sampler_inst.html
>
>
>And in case anyone forgets, the portal-like Forrest front page in CVS,
>using lots of CSS:
>
>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/layout/xml.apache.org/home.html?rev=1.3
>
>
>--Jeff
>
>
> > Bert
> >
css skins (Re: forrest war)
Posted by Jeff Turner <je...@apache.org>.
On Sat, Nov 09, 2002 at 03:25:14PM +0100, Bert Van Kets wrote:
...
> I'm building the new skin using as much CSS as possible. IMHO This will be
> the most beautiful and fastest skin ever built for Forrest. :-)
Wohoo :)
FYI, over the next few days I'm planning on factoring stuff out of the
forrest-site and avalon-tigris skins into a common repository, and
generally fixing the stylesheets. The aim is to make skin maintenance
less of a PITA. If you're in the early stages of design this won't
affect you.. hopefully the XSLTs will be less horrible by the time you
get to them.
Rounding up recent CSS skin stuff:
Robert Koberg:
"If you all want, we can use the livestoryboard.com site as a base for
a forrest skin. We have put ALOT of work into the layout/css. The site
can look extremely different by simply changing the CSS."
<AD...@koberg.com>
The tigris skin mentioned earlier:
http://style.tigris.org/nonav/dev/docs/sampler_inst.html
And in case anyone forgets, the portal-like Forrest front page in CVS,
using lots of CSS:
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/layout/xml.apache.org/home.html?rev=1.3
--Jeff
> Bert
>
Re: forrest war
Posted by Bert Van Kets <be...@vankets.com>.
At 01:12 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 02:50:36PM +0100, Bert Van Kets wrote:
> > At 00:48 10/11/2002 +1100, you wrote:
> > >On Sat, Nov 09, 2002 at 02:32:09PM +0100, Bert Van Kets wrote:
> > >...
> > >> >I'll look into adding a conditional copy based on JDK version. In the
> > >> >meanwhile, try copying lib/endorsed/* into
> build/webapp/WEB-INF/lib, and
> > >> >then generate a war with 'jar cvf ../mysite.war' in the webapp/
> > >
> > >Should be:
> > >
> > > jar cvf ../mysite.war *
> > >
> > >--Jeff
> >
> > I figured this one out myself ;-)
> > The hack works now on JDK 1.3.1_02.
> > Man, what a difference in working with Forrest compared to a few months
> > ago. I really need to start from scratch again. And I haven't even
> > touched the Forrestbot yet, which I would like to use too to ftp my
> > data to the server.
>
>Forrestbot works, mostly. It can be demonstrated by typing 'forrestbot
>-Dbot.config=<config file>' in the src/resources/forrestbot/samples/
>directory. It's kinda neat being able to go from just an XML file to
>having a herd of projects checked out and built :) Ideal for regression
>suites..
I'll be using it for 1 site only for now.
I'm building the new skin using as much CSS as possible. IMHO This will be
the most beautiful and fastest skin ever built for Forrest. :-)
Bert
>--Jeff
Re: forrest war
Posted by Jeff Turner <je...@apache.org>.
On Sat, Nov 09, 2002 at 02:50:36PM +0100, Bert Van Kets wrote:
> At 00:48 10/11/2002 +1100, you wrote:
> >On Sat, Nov 09, 2002 at 02:32:09PM +0100, Bert Van Kets wrote:
> >...
> >> >I'll look into adding a conditional copy based on JDK version. In the
> >> >meanwhile, try copying lib/endorsed/* into build/webapp/WEB-INF/lib, and
> >> >then generate a war with 'jar cvf ../mysite.war' in the webapp/
> >
> >Should be:
> >
> > jar cvf ../mysite.war *
> >
> >--Jeff
>
> I figured this one out myself ;-)
> The hack works now on JDK 1.3.1_02.
> Man, what a difference in working with Forrest compared to a few months
> ago. I really need to start from scratch again. And I haven't even
> touched the Forrestbot yet, which I would like to use too to ftp my
> data to the server.
Forrestbot works, mostly. It can be demonstrated by typing 'forrestbot
-Dbot.config=<config file>' in the src/resources/forrestbot/samples/
directory. It's kinda neat being able to go from just an XML file to
having a herd of projects checked out and built :) Ideal for regression
suites..
--Jeff
Re: forrest war
Posted by Bert Van Kets <be...@vankets.com>.
At 00:48 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 02:32:09PM +0100, Bert Van Kets wrote:
>...
> > >I'll look into adding a conditional copy based on JDK version. In the
> > >meanwhile, try copying lib/endorsed/* into build/webapp/WEB-INF/lib, and
> > >then generate a war with 'jar cvf ../mysite.war' in the webapp/
>
>Should be:
>
> jar cvf ../mysite.war *
>
>--Jeff
I figured this one out myself ;-)
The hack works now on JDK 1.3.1_02.
Man, what a difference in working with Forrest compared to a few months
ago. I really need to start from scratch again. And I haven't even
touched the Forrestbot yet, which I would like to use too to ftp my data to
the server.
Thanks,
Bert
>
> > I'll try that.
> > Bert
> >
Re: forrest war
Posted by Jeff Turner <je...@apache.org>.
On Sat, Nov 09, 2002 at 02:32:09PM +0100, Bert Van Kets wrote:
...
> >I'll look into adding a conditional copy based on JDK version. In the
> >meanwhile, try copying lib/endorsed/* into build/webapp/WEB-INF/lib, and
> >then generate a war with 'jar cvf ../mysite.war' in the webapp/
Should be:
jar cvf ../mysite.war *
--Jeff
> I'll try that.
> Bert
>
Re: forrest war
Posted by Bert Van Kets <be...@vankets.com>.
At 00:25 10/11/2002 +1100, you wrote:
>On Sat, Nov 09, 2002 at 01:19:52PM +0100, Bert Van Kets wrote:
> > Hi guys,
> > I am trying to get in pace with the recent Forrest development. Man, has
> > this project moved since I created the skin.
> >
> > I did a completely fresh checkout and tried the "Forrest seed", "Forrest"
> > and Forrest war" commands and have two problems.
> >
> > 1. The dynamic links in the generated site are not correct. The selected
> > menu item is not yellow, like it should be. Haven't had the time to check
> > out why yet.
>
>Having a look now.
> >
> > 2. After building the war file and starting it up in Tomcat I get an
> > Internal Server error. Here's the stack trace:
>...
> > java.lang.NoClassDefFoundError: javax/xml/transform/URIResolver
> > at java.lang.ClassLoader.defineClass0(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
>
>Hmm.. I think it's a bug. Are you running JDK 1.3?
Yes I am version 1.3.1_02 on Win2K Server SP3
>Forrest currently doesn't include XML-related jars (xml-apis, xerces,
>xalan) in the war (or webapp). In JDK 1.4, these are provided by the
>JDK, through the -Djava.endorsed.dirs property.
>
>I hadn't considered 1.3 though, where the webapp would presumably break
>:/
>
>I'll look into adding a conditional copy based on JDK version. In the
>meanwhile, try copying lib/endorsed/* into build/webapp/WEB-INF/lib, and
>then generate a war with 'jar cvf ../mysite.war' in the webapp/
>directory.
I'll try that.
Bert
>--Jeff
Re: forrest war
Posted by Jeff Turner <je...@apache.org>.
On Sat, Nov 09, 2002 at 01:19:52PM +0100, Bert Van Kets wrote:
> Hi guys,
> I am trying to get in pace with the recent Forrest development. Man, has
> this project moved since I created the skin.
>
> I did a completely fresh checkout and tried the "Forrest seed", "Forrest"
> and Forrest war" commands and have two problems.
>
> 1. The dynamic links in the generated site are not correct. The selected
> menu item is not yellow, like it should be. Haven't had the time to check
> out why yet.
Fixed.
> 2. After building the war file and starting it up in Tomcat I get an
> Internal Server error. Here's the stack trace:
Will have a tinker tomorrow..
--Jeff
Re: forrest war
Posted by Jeff Turner <je...@apache.org>.
On Sat, Nov 09, 2002 at 01:19:52PM +0100, Bert Van Kets wrote:
> Hi guys,
> I am trying to get in pace with the recent Forrest development. Man, has
> this project moved since I created the skin.
>
> I did a completely fresh checkout and tried the "Forrest seed", "Forrest"
> and Forrest war" commands and have two problems.
>
> 1. The dynamic links in the generated site are not correct. The selected
> menu item is not yellow, like it should be. Haven't had the time to check
> out why yet.
Having a look now.
>
> 2. After building the war file and starting it up in Tomcat I get an
> Internal Server error. Here's the stack trace:
...
> java.lang.NoClassDefFoundError: javax/xml/transform/URIResolver
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
Hmm.. I think it's a bug. Are you running JDK 1.3?
Forrest currently doesn't include XML-related jars (xml-apis, xerces,
xalan) in the war (or webapp). In JDK 1.4, these are provided by the
JDK, through the -Djava.endorsed.dirs property.
I hadn't considered 1.3 though, where the webapp would presumably break
:/
I'll look into adding a conditional copy based on JDK version. In the
meanwhile, try copying lib/endorsed/* into build/webapp/WEB-INF/lib, and
then generate a war with 'jar cvf ../mysite.war' in the webapp/
directory.
--Jeff