from:"Rob Finneran"

RE: Cocoon and Jetty

2002-03-03 Thread Rob Finneran

Hello Listees,

I remember Brad from seeing him on the Jetty list. He helped me out one day
when I was having some problems - so I think he's a good guy, despite his
frustrations.

As for my own experience with Cocoon:

I can report success with C2 and the JBoss-2.4.4/Jetty-3.1.3 combination
"right out of the box".

The real trick was for me to get Xerces working with
JBoss-2.4.4/Jetty-3.1.3. After I accomplished that, I simply copied the
cocoon .war file to the JBoss deploy directory and then it was working fine.

While I think Python and Zope are good tools, I prefer the power and
flexibility of the Java-based open-source solutions.

Rob

-Original Message-
From: Brad Cox [mailto:[EMAIL PROTECTED]]
Sent: Saturday, March 02, 2002 7:34 AM
To: [EMAIL PROTECTED]
Subject: RE: Cocoon and Jetty

At 11:11 AM +0100 3/2/02, giacomo wrote:
>>  After wasting this whole week trying  to get Cocoon out of the box
>>  with not one suggestions from cocoon developers, I'm beginning to get
>>  the message.
>
>Maybe you missed the reply from Vadim. He *is* a cocoon developer.

Then my apologies to Vadim. This was not apparent from his sig.

>Finally my suggestion to you would be try it on another servlet engine
>as my experience is that is usually *does* run out of the box following
>the installation guidlines from the documents.

As I said, the problem is not with Jetty. I've tried it with two
versions of tomcat with similar results to those reported below.

I'm not interested in "taking anything out" on this list. I'm
interested in getting my app on the air, while repaying the help I
did receive (largely) from users with a bread crumb trail to zope,
which  appears to be a superior alternative to cocoon that DOES work
out of the box and does have support from its developers. Bye now.

On Friday 01 March 2002 03:17 pm, Anthony W. Marino wrote:
>Under a regular user acct, I've reinstalled the latest cocoon(cvs) dist
with
>several different releases of TC4 (4.01,4.02, 4.03, 4.10) with NO positive
>results.
>The above log results remain the same.

--
Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751
o For industrial age goods there were checks and credit cards.
For everything else there is http://virtualschool.edu/mybank
o Java Interactive Learning Environment http://virtualschool.edu/jile
o Java Web Application Architecture: http://virtualschool.edu/jwaa

-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

RE: Cocoon and Jetty??

2002-03-01 Thread Rob Finneran


Just for fun, eliminate cocoon and test it anyway.
Also either rebuild the cocoon jar without the xml parser stuff or remove it
from the jetty/webapps/WEB-INF/lib.

You might try asking this question on the Xerces-J user list, even if it is
a cocoon issue, they would immediately understand the parser error messages.

Good Luck!


-Original Message-
From: Brad Cox [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: RE: Cocoon and Jetty??


At 1:14 PM -0800 3/1/02, Rob Finneran wrote:
>Well, I'm not really sure, but my hunch still is that it's still picking up
>the either the  crimson stuff or a different version of JAXP (now I really
>don't know much about what I'm talking about!)

I don't think so, see below:

>Somewhere you classpath is picking up something from the wrong libriaries.
>That's why I recommened that you more closely control your classpath. I
>thought I've seen this problem before, if I remember correctly. It occurs
>not only with Jetty, but Tomcat as well. Also, be careful that these API
are
>not loaded from your JAVA_HOME/lib/ext directory either.

Will check that next. I've since downloaded tomcat 4.0.2 AND AM
GETTING EXACTLY THE SAME PROBLEM.

>BTW, the .war should be expanded to the webapps/cocoon directory and not
the
>webapps/war/cocoon. But I don't think this is your first problem, In fact I
>would bet that your problem is with completly replacing the Crimson
>processor with Xerces. Try removing cocoon completly and just get Jetty to
>work with Xerces first.

I've been using xerces, xalan and velocity with jetty in my own
webapps previously so I know jetty works properly with thse. I've
eliminated everything but cocoon from webapps by now just to be safe.

The jetty DEBUG output explicitly lists the jars its examining:

12:21:25.234 DEBUG  try findClass
org.apache.jasper.servlet.JspServlet from

file:/jetty/webapps/cocoon/WEB-INF/lib/javac.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/avalon-scratchpad-20020212.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/xalan-2.3.1.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jakarta-regexp-1.2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/avalon-framework-4.1.2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/logkit-1.0.1.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/commons-collections-1.0.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/xerces.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/xml-apis.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/commons-httpclient-20011012.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/avalon-excalibur-4.1.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/fop-0.20.3rc.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/xmldb-api-2001.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jimi-1.0.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/hsqldb-1.61.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/batik-libs-1.1.1.jar,
file:/jetty/webapps/cocoon
/WEB-INF/lib/velocity-1.2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/resolver-20020130.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/rhino-1.5r3.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/xt-19991105.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jstyle.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/maybeupload_1-0-5pre3.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/lucene-1.2-rc2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/rdffilter.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jisp_1_0_2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/deli-0.43.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/bsf-2.2.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jena-1.3.0.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/jtidy-04aug2000r7-dev.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/pizza-1.1.jar,
file:/jetty/webapps/cocoon/WEB-INF/lib/cocoon-2.0.2-dev.jar,
file:/jetty/webapps/cocoon/WEB-INF/classes/


>-Original Message-
>From: Brad Cox [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 01, 2002 8:16 AM
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Greg
>Wilkins
>Subject: RE: Cocoon and Jetty??
>
>
>At 5:49 PM -0800 2/28/02, Rob Finneran wrote:
>>Hey Brad nice to see you around again,
>
>And thanks for the help! But after making all of your changes, I'm
>still getting exactly the same problem. See possible clue towards the
>end. I've also downloaded the latest version of xerces (was using the
>beta before) and installed that as instructed in jetty/lib and
>cocoon/war/WEB-INF/lib.
>
>At 10:57 AM -0500 3/1/02, Brad Cox wrote:
>>Cocoon 2 - Internal server error
>>type fatal
>>message SAX2 driver class org.apache.xerces.parsers.SAXParser does
>>not implement XMLReader
>>description java.lang.ClassCastException:
>>org.apache.xerces.parsers.StandardParserConfiguration
>>sender org.apache.cocoon.servlet.CocoonServlet
>>source Cocoon servlet
>>stack-trace
>>java.lang.ClassCastException:
>&

RE: Cocoon and Jetty??

2002-03-01 Thread Rob Finneran


Just another thought -

Some older versions of crimson come with funny names like parsers.jar, etc.
Maybe this will help??


-Original Message-
From: Rob Finneran [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 1:14 PM
To: [EMAIL PROTECTED]
Subject: RE: Cocoon and Jetty??


Well, I'm not really sure, but my hunch still is that it's still picking up
the either the  crimson stuff or a different version of JAXP (now I really
don't know much about what I'm talking about!)

Its my understanding that the relevant JAXP and SAX API are all built into
the two Xerces 2.0 jars.

Somewhere you classpath is picking up something from the wrong libriaries.
That's why I recommened that you more closely control your classpath. I
thought I've seen this problem before, if I remember correctly. It occurs
not only with Jetty, but Tomcat as well. Also, be careful that these API are
not loaded from your JAVA_HOME/lib/ext directory either.

BTW, the .war should be expanded to the webapps/cocoon directory and not the
webapps/war/cocoon. But I don't think this is your first problem, In fact I
would bet that your problem is with completly replacing the Crimson
processor with Xerces. Try removing cocoon completly and just get Jetty to
work with Xerces first.

Good Luck!






-Original Message-
From: Brad Cox [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 8:16 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Greg
Wilkins
Subject: RE: Cocoon and Jetty??


At 5:49 PM -0800 2/28/02, Rob Finneran wrote:
>Hey Brad nice to see you around again,

And thanks for the help! But after making all of your changes, I'm
still getting exactly the same problem. See possible clue towards the
end. I've also downloaded the latest version of xerces (was using the
beta before) and installed that as instructed in jetty/lib and
cocoon/war/WEB-INF/lib.

At 10:57 AM -0500 3/1/02, Brad Cox wrote:
>Cocoon 2 - Internal server error
>type fatal
>message SAX2 driver class org.apache.xerces.parsers.SAXParser does
>not implement XMLReader
>description java.lang.ClassCastException:
>org.apache.xerces.parsers.StandardParserConfiguration
>sender org.apache.cocoon.servlet.CocoonServlet
>source Cocoon servlet
>stack-trace
>java.lang.ClassCastException:
>org.apache.xerces.parsers.StandardParserConfiguration
>   at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
>   at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
>   at
>org.apache.cocoon.components.language.markup.AbstractMarkupLanguage.generat
eCode(AbstractMarkupLanguage.java:377)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.genera
teResource(ProgramGeneratorImpl.java:368)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.create
Resource(ProgramGeneratorImpl.java:331)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(P
rogramGeneratorImpl.java:294)
>   at org.apache.cocoon.sitemap.Handler.run(Handler.java:270)
>   at java.lang.Thread.run(Thread.java:498)

Here's my ~/.jettrc

export JAVA_HOME="/jdk"
export JAVA="$JAVA_HOME/bin/java"
export JETTY_HOME="/jetty"
export JETTY_OPTIONS="-DDEBUG \

-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBu
ilderFactoryImpl\

-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory
Impl\

-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl\
"
export
JAVA_OPTIONS="\

-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBu
ilderFactoryImpl\

-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory
Impl\

-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl\
"

Which (I think) is the same as your instructions. The only thing in
jetty/webaps at this point is cocoon/war; all my webapps are removed.

[bcox@linux:/jetty/webapps]$ d /jetty/webapps
total 0
lrwxrwxrwx1 bcox wheel  12 Feb 28 11:30 cocoon ->
/cocoon/war/

[bcox@linux:/jetty/webapps]$ d /jetty/lib
total 1264
-rw-r--r--1 bcox wheel  474421 Oct 21 08:57 com.sun.net.ssl.jar
-rw-r--r--1 bcox wheel   75163 Feb 28 12:56 javax.servlet.jar
-rw-r--r--1 bcox wheel  277370 Feb 28 12:56
org.apache.jasper.jar
-rw-r--r--1 bcox wheel  453817 Feb 28 12:56
org.mortbay.jetty.jar
lrwxrwxrwx1 bcox wheel  28 Mar  1 10:18 parser.jar ->
/xerces/build/xercesImpl.jar
lrwxrwxrwx1 bcox wheel  39 Feb 28 16:53
xalan-2.3.1.jar -> /cocoon/war/WEB-INF/lib/xalan-2.3.1.jar
lrwxrwxrwx1 bcox wheel  31 Mar  1 10:17
xmlParserAPIs.jar -> /xerces/build/xmlParserAPIs.jar
drwxr-xr-x6 bcox wheel1024 F

RE: Cocoon and Jetty??

2002-03-01 Thread Rob Finneran


Well, I'm not really sure, but my hunch still is that it's still picking up
the either the  crimson stuff or a different version of JAXP (now I really
don't know much about what I'm talking about!)

Its my understanding that the relevant JAXP and SAX API are all built into
the two Xerces 2.0 jars.

Somewhere you classpath is picking up something from the wrong libriaries.
That's why I recommened that you more closely control your classpath. I
thought I've seen this problem before, if I remember correctly. It occurs
not only with Jetty, but Tomcat as well. Also, be careful that these API are
not loaded from your JAVA_HOME/lib/ext directory either.

BTW, the .war should be expanded to the webapps/cocoon directory and not the
webapps/war/cocoon. But I don't think this is your first problem, In fact I
would bet that your problem is with completly replacing the Crimson
processor with Xerces. Try removing cocoon completly and just get Jetty to
work with Xerces first.

Good Luck!






-Original Message-
From: Brad Cox [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 8:16 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Greg
Wilkins
Subject: RE: Cocoon and Jetty??


At 5:49 PM -0800 2/28/02, Rob Finneran wrote:
>Hey Brad nice to see you around again,

And thanks for the help! But after making all of your changes, I'm
still getting exactly the same problem. See possible clue towards the
end. I've also downloaded the latest version of xerces (was using the
beta before) and installed that as instructed in jetty/lib and
cocoon/war/WEB-INF/lib.

At 10:57 AM -0500 3/1/02, Brad Cox wrote:
>Cocoon 2 - Internal server error
>type fatal
>message SAX2 driver class org.apache.xerces.parsers.SAXParser does
>not implement XMLReader
>description java.lang.ClassCastException:
>org.apache.xerces.parsers.StandardParserConfiguration
>sender org.apache.cocoon.servlet.CocoonServlet
>source Cocoon servlet
>stack-trace
>java.lang.ClassCastException:
>org.apache.xerces.parsers.StandardParserConfiguration
>   at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
>   at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
>   at
>org.apache.cocoon.components.language.markup.AbstractMarkupLanguage.generat
eCode(AbstractMarkupLanguage.java:377)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.genera
teResource(ProgramGeneratorImpl.java:368)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.create
Resource(ProgramGeneratorImpl.java:331)
>   at
>org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(P
rogramGeneratorImpl.java:294)
>   at org.apache.cocoon.sitemap.Handler.run(Handler.java:270)
>   at java.lang.Thread.run(Thread.java:498)

Here's my ~/.jettrc

export JAVA_HOME="/jdk"
export JAVA="$JAVA_HOME/bin/java"
export JETTY_HOME="/jetty"
export JETTY_OPTIONS="-DDEBUG \

-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBu
ilderFactoryImpl\

-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory
Impl\

-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl\
"
export
JAVA_OPTIONS="\

-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBu
ilderFactoryImpl\

-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory
Impl\

-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl\
"

Which (I think) is the same as your instructions. The only thing in
jetty/webaps at this point is cocoon/war; all my webapps are removed.

[bcox@linux:/jetty/webapps]$ d /jetty/webapps
total 0
lrwxrwxrwx1 bcox wheel  12 Feb 28 11:30 cocoon ->
/cocoon/war/

[bcox@linux:/jetty/webapps]$ d /jetty/lib
total 1264
-rw-r--r--1 bcox wheel  474421 Oct 21 08:57 com.sun.net.ssl.jar
-rw-r--r--1 bcox wheel   75163 Feb 28 12:56 javax.servlet.jar
-rw-r--r--1 bcox wheel  277370 Feb 28 12:56
org.apache.jasper.jar
-rw-r--r--1 bcox wheel  453817 Feb 28 12:56
org.mortbay.jetty.jar
lrwxrwxrwx1 bcox wheel  28 Mar  1 10:18 parser.jar ->
/xerces/build/xercesImpl.jar
lrwxrwxrwx1 bcox wheel  39 Feb 28 16:53
xalan-2.3.1.jar -> /cocoon/war/WEB-INF/lib/xalan-2.3.1.jar
lrwxrwxrwx1 bcox wheel  31 Mar  1 10:17
xmlParserAPIs.jar -> /xerces/build/xmlParserAPIs.jar
drwxr-xr-x6 bcox wheel1024 Feb 28 18:29 z

[bcox@linux:/jetty/webapps]$ d /cocoon/war/WEB-INF/lib/
total 14411
-rw-r--r--1 bcox wheel  196490 Feb 28 15:45
avalon-excalibur-4.1.jar
-rw-r--r--1 bcox wheel   47564 Feb 28 15:45
avalon-framework-4.1.2.jar
-rw-r--r--1 bcox wheel  242984 Feb 2

RE: Cocoon and Jetty??

2002-02-28 Thread Rob Finneran


Hey Brad nice to see you around again,

Take it step by step. First completely replace crimson with xerces as your
xml parser.

Remove javax.xml.jaxp.jar and org.apache.crimson.jar from jetty/lib.
Then make sure jetty loads fine WITHOUT Crimson before attempting to use
cocoon.

Although these lines come from my jboss/bin/run.bat file, they should still
be elpful.
The settings are pretty much universal:

REM *** tools.jar needs to be in CLASSPATH for JSP's to compile:
set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;/jdk1.3.1_02/lib/tools.jar

REM *** Latest Xerces and Xalan (I downloaded and installed seperatly from
C2:
REM  Xerces-2_0_0 and Xalan-j_2_3_0 Configuration 
set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;/src/xerces-2_0_0/xercesImpl.jar
set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;/src/xerces-2_0_0/xmlParserAPIs.jar
set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;/src/Xalan-j_2_3_0/bin/xalan.jar

REM set up jaxp properties to reference parser and transformer
implementations:
set
JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.Docum
entBuilderFactoryImpl
set
JAXP=%JAXP% -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXP
arserFactoryImpl
set
JAXP=%JAXP% -Djavax.xml.transform.TransformerFactory=org.apache.xalan.proces
sor.TransformerFactoryImpl

REM Here how I start JBOSS:
java %JAXP% -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %1 %2 %3 %4 %5 %6
%7 %8 %9

Hope this helps!!

Rob

-Original Message-
From: Brad Cox [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 5:31 PM
To: [EMAIL PROTECTED]
Subject: RE: Cocoon and Jetty??


I'm still unable to get cocoon running on jetty. Been at it all day.

I'm using the CVS version of xml-cocoon, built according to
instructions. I've replaced all xalan, xercse, crimson, and xml-api
files in /jetty/lib with those from cocoon, and done everything else
recommended in the article (below). Yes, I've removed the build
directory (which is in /tmp in jetty's case).

Current symptoms follow. Looks like a classloader problem but danged
if I can find it.

type fatal

message SAX2 driver class org.apache.xerces.parsers.SAXParser does
not implement XMLReader

description java.lang.ClassCastException:
org.apache.xerces.parsers.StandardParserConfiguration

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

stack-trace

java.lang.ClassCastException:
org.apache.xerces.parsers.StandardParserConfiguration
at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source)
at
org.apache.cocoon.components.language.markup.AbstractMarkupLanguage.generate
Code(AbstractMarkupLanguage.java:377)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.generat
eResource(ProgramGeneratorImpl.java:368)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR
esource(ProgramGeneratorImpl.java:331)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr
ogramGeneratorImpl.java:294)
at org.apache.cocoon.sitemap.Handler.run(Handler.java:270)
at java.lang.Thread.run(Thread.java:498)


request-uri

/cocoon/


path-info

At 11:02 AM -0500 2/28/02, Vadim Gritsenko wrote:
>Apparently you had previous version of Cocoon.
>http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=101183982808469&w=2
>Read solution number (6)
>
>Vadim
>
>>  -Original Message-
>>  From: Brad Cox [mailto:[EMAIL PROTECTED]]
>>  Sent: Thursday, February 28, 2002 9:50 AM
>>  To: [EMAIL PROTECTED]
>>  Subject: Cocoon and Jetty??
>>
>>  I'm new to cocoon. Just downloaded it yesterday and can't get it to
>run.
>>
>>  AFAIK Jetty doesn't expand wars, so I expanded it manually into
>>  /cocoon/war. /cocoon and /jetty are symlinks to /usr/local/realdir.
>>  Configured jetty to treat /cocoon/war as a webapp as always. In
>>  particular, in /etc/jetty.xml:
>>
>>  
>>  /cocoon/*
>>  /cocoon/war/
>>  /jetty/etc/webdefault.xml
>>  false
>>  
>>
>>  and in apache's httpd.conf add.
>>
>>  ProxyPass /cocoon http://localhost:8080/cocoon
>>
>>  I built cocoon as described in the install, modified to use jetty
>>  instead of tomcat:
>>
>>  ./build.sh  -Dinclude.webapp.libs=yes
>>  -Dinstall.war=/jetty/webapps webapp
>>
>>  The Jetty logs are normal except that they now show Server 1.6 on the
>>  air, hit ^C to abort, presumably from cocoon.
>>
>>  All this on Linux RH 7.0, Jetty (latest), and IBM SDK 1.3.1 (latest).
>>  For Cocoon, same results with the release version and via CVS
>>  checkout/rebuild.
>>
>>  Can someone help me get on the air?
>>
>>  sitemap.log
>>
>>  ERROR   (2002-02-28) 09:28.11:234   [sitemap](/cocoon/)
>>  SocketListener-0/Handler: Error compiling sitemap
>>  java.lang.NoSuchFieldError:
>>  org.apache.cocoon.sitemap.AbstractSitemap: field manager not found
>>  at
>org.apache.cocoon.www.sitemap_xmap.confi

RE: Cocoon and Jetty

RE: Cocoon and Jetty??

RE: Cocoon and Jetty??

RE: Cocoon and Jetty??

RE: Cocoon and Jetty??

5 matches

Site Navigation

Mail list logo

Footer information