RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Title: RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Many
thanks, it now works.
Is it
possible to add this last comment to the install
instructions?
Gilles
-Original Message-From: Michael Zehrer
[mailto:[EMAIL PROTECTED]]Sent: mercredi, 21. novembre 2001
09:38To: [EMAIL PROTECTED]Subject: AW: Cocoon
and WEBSPHERE 3.5 Fixpack 3.4.2
Hi
Gilles,
there is a problem with all statements. I
don't know why, but for the welcome example you have to change the
mapping
from
to , then it works.
Can
someone explain what could be wrong?
Michael
-Ursprüngliche Nachricht-Von: Ducret, Gilles (CH)
[mailto:[EMAIL PROTECTED]]Gesendet: Montag, 19.
November 2001 10:59An:
'[EMAIL PROTECTED]'Betreff: RE: Cocoon and WEBSPHERE
3.5 Fixpack 3.4.2
Hello Jack,
Your instructions really helped.
We now have the problem: when we access the URL, it seems
that it is redirected to a welcome page.
We have the message that this ressource is not found.
Any idea about that?
We can see that it is now running (from the traces) but the
welcome page/ressource is not found.
Is there something else that has to be defined?
Many thanks
Gilles
-Original Message- From:
Jack Hirasawa [mailto:[EMAIL PROTECTED]]
Sent: vendredi, 16. novembre 2001 15:51 To: [EMAIL PROTECTED] Subject: Re:
Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Hi Gilles,
Have you checked the mail archives? You should check
there first before asking (they are in
there).
But enough nagging, to make your life easier here's the
instructions again for Cocoon2...
1) If there's a Cocoon-2.0rc1\build directory, delete
it 2) set
JAVA_HOME=c:\WebSphere\AppServer\jdk 3) .\build.bat
-Dinclude.webapp.libs=yes -Dinstall.war=c:\WebSphere\AppServer\hosts\default_host\cocoon
webapp 4) Fire Up the Websphere admin server and the
Admin console 5) Go to the Servlet Container and put
it in Servlet 2.2 full compliance mode
6) Deploy the WAR file in c:\Cocoon-2.0rc1\build\cocoon
(use Convert a WAR File) 7)
Update the Server Command Line Arguments: -Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser
-classpath C:\Cocoon-2.0rc1\lib\xerces_1_4_3.jar;C:\Cocoon-2.0rc1\lib\cocoon-2.0rc1.jar;C:\Cocoon-2.0rc1\lib\velocity-1.1.jar;C:\Cocoon-2.0rc1\lib\servlet_2_2.jar;C:\Cocoon-2.0rc1\lib\maybeupload.jar;C:\Cocoon-2.0rc1\lib\batik-libs.jar;C:\Cocoon-2.0rc1\lib\ant_1_4.jar;C:\Cocoon-2.0rc1\lib\xalan-2.2.0-dev.jar;C:\Cocoon-2.0rc1\lib\logkit-1.0b5.jar;C:\Cocoon-2.0rc1\lib\fop-0_20_1-dev.jar;C:\Cocoon-2.0rc1\lib\resolver.jar;C:\Cocoon-2.0rc1\lib\ant_1_4-optional.jar;C:\Cocoon-2.0rc1\lib\avalon-framework-4.0.jar;C:\Cocoon-2.0rc1\lib\jakarta-regexp-1.2.jar;C:\Cocoon-2.0rc1\lib\dom2.jar;C:\Cocoon-2.0rc1\lib\rhino.jar;C:\Cocoon-2.0rc1\lib\xt.jar;C:\Cocoon-2.0rc1\lib\hsqldb-1.61.jar;C:\Cocoon-2.0rc1\lib\avalon-excalibur-4.0.jar;C:\Cocoon-2.0rc1\lib\Tidy.jar;C:\Cocoon-2.0rc1\lib\stylebook-1.0-b3_xalan-2.jar;C:\Cocoon-2.0rc1\lib\junit.jar;C:\Cocoon-2.0rc1\lib\jimi-1.0.jar;C:\Cocoon-2.0rc1\lib\jstyle.jar;C:\Cocoo
n-2.0rc1\lib\bsf.jar;C:/WebSphere/AppServer/jdk/lib/tools.jar;c:\WebSphere\AppServer\hosts\default_host\cocoon\servlets\cocoon-2.0rc1.jar
8) Select the Servlet Cocoon2 and Add a Servlet Web Path
/cocoon/* 9) On the advanced tab add the following init parameters
org.apache.cocoon.component.parser.Parser=org.apache.cocoon.components.parser.XercesParser
force-load=com.ibm.servlet.classloader.Handler
classpath-attribute=com.ibm.websphere.servlet.application.classpath
10) In the Web directory of the Webapp edit cocoon.xconf
and move the parser statement out of the comment
block 11) Copy the WEB-INF directory from the web
directory to the servlets directory 12) Copy the cocoon.xconf file from the web directory to the servlets
directory 12) Shut down the
Admin console 13) Shut down the Admin server and
restart it 14) Restart the admin console
15) Start the server
For step 7) you should really probably use the jar files
that get deployed in the servlets directory instead
of the ones in the build directory.
Hope this helps. If you're trying to get cocoon 1.8.2
working, check the archives, I got it working a
while ago and I used the tips in the archives.
Jack
>From: "Ducret, Gilles (CH)"
<[EMAIL PROTECTED]> >Reply-To:
[EMAIL PROTECTED] >To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
>Date: Fri, 16 Nov 2001 10:10:00 +0100 >MIME-Version: 1.0 >Received: from
[64.125.133.20] by hotmail.com (3.2) with ESMTP id >MHotMailBDBE23B100
AW: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Title: RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hi Gilles, there is a problem with all statements. I don't know why, but for the welcome example you have to change the mapping from to , then it works. Can someone explain what could be wrong? Michael -Ursprüngliche Nachricht-Von: Ducret, Gilles (CH) [mailto:[EMAIL PROTECTED]]Gesendet: Montag, 19. November 2001 10:59An: '[EMAIL PROTECTED]'Betreff: RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hello Jack, Your instructions really helped. We now have the problem: when we access the URL, it seems that it is redirected to a welcome page. We have the message that this ressource is not found. Any idea about that? We can see that it is now running (from the traces) but the welcome page/ressource is not found. Is there something else that has to be defined? Many thanks Gilles -Original Message- From: Jack Hirasawa [mailto:[EMAIL PROTECTED]] Sent: vendredi, 16. novembre 2001 15:51 To: [EMAIL PROTECTED] Subject: Re: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hi Gilles, Have you checked the mail archives? You should check there first before asking (they are in there). But enough nagging, to make your life easier here's the instructions again for Cocoon2... 1) If there's a Cocoon-2.0rc1\build directory, delete it 2) set JAVA_HOME=c:\WebSphere\AppServer\jdk 3) .\build.bat -Dinclude.webapp.libs=yes -Dinstall.war=c:\WebSphere\AppServer\hosts\default_host\cocoon webapp 4) Fire Up the Websphere admin server and the Admin console 5) Go to the Servlet Container and put it in Servlet 2.2 full compliance mode 6) Deploy the WAR file in c:\Cocoon-2.0rc1\build\cocoon (use Convert a WAR File) 7) Update the Server Command Line Arguments: -Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser -classpath C:\Cocoon-2.0rc1\lib\xerces_1_4_3.jar;C:\Cocoon-2.0rc1\lib\cocoon-2.0rc1.jar;C:\Cocoon-2.0rc1\lib\velocity-1.1.jar;C:\Cocoon-2.0rc1\lib\servlet_2_2.jar;C:\Cocoon-2.0rc1\lib\maybeupload.jar;C:\Cocoon-2.0rc1\lib\batik-libs.jar;C:\Cocoon-2.0rc1\lib\ant_1_4.jar;C:\Cocoon-2.0rc1\lib\xalan-2.2.0-dev.jar;C:\Cocoon-2.0rc1\lib\logkit-1.0b5.jar;C:\Cocoon-2.0rc1\lib\fop-0_20_1-dev.jar;C:\Cocoon-2.0rc1\lib\resolver.jar;C:\Cocoon-2.0rc1\lib\ant_1_4-optional.jar;C:\Cocoon-2.0rc1\lib\avalon-framework-4.0.jar;C:\Cocoon-2.0rc1\lib\jakarta-regexp-1.2.jar;C:\Cocoon-2.0rc1\lib\dom2.jar;C:\Cocoon-2.0rc1\lib\rhino.jar;C:\Cocoon-2.0rc1\lib\xt.jar;C:\Cocoon-2.0rc1\lib\hsqldb-1.61.jar;C:\Cocoon-2.0rc1\lib\avalon-excalibur-4.0.jar;C:\Cocoon-2.0rc1\lib\Tidy.jar;C:\Cocoon-2.0rc1\lib\stylebook-1.0-b3_xalan-2.jar;C:\Cocoon-2.0rc1\lib\junit.jar;C:\Cocoon-2.0rc1\lib\jimi-1.0.jar;C:\Cocoon-2.0rc1\lib\jstyle.jar;C:\Cocoo n-2.0rc1\lib\bsf.jar;C:/WebSphere/AppServer/jdk/lib/tools.jar;c:\WebSphere\AppServer\hosts\default_host\cocoon\servlets\cocoon-2.0rc1.jar 8) Select the Servlet Cocoon2 and Add a Servlet Web Path /cocoon/* 9) On the advanced tab add the following init parameters org.apache.cocoon.component.parser.Parser=org.apache.cocoon.components.parser.XercesParser force-load=com.ibm.servlet.classloader.Handler classpath-attribute=com.ibm.websphere.servlet.application.classpath 10) In the Web directory of the Webapp edit cocoon.xconf and move the parser statement out of the comment block 11) Copy the WEB-INF directory from the web directory to the servlets directory 12) Copy the cocoon.xconf file from the web directory to the servlets directory 12) Shut down the Admin console 13) Shut down the Admin server and restart it 14) Restart the admin console 15) Start the server For step 7) you should really probably use the jar files that get deployed in the servlets directory instead of the ones in the build directory. Hope this helps. If you're trying to get cocoon 1.8.2 working, check the archives, I got it working a while ago and I used the tips in the archives. Jack >From: "Ducret, Gilles (CH)" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 >Date: Fri, 16 Nov 2001 10:10:00 +0100 >MIME-Version: 1.0 >Received: from [64.125.133.20] by hotmail.com (3.2) with ESMTP id >MHotMailBDBE23B1009940042A18407D851404FD0; Fri, 16 Nov 2001 01:13:23 -0800 >Received: (qmail 84477 invoked by uid 500); 16 Nov 2001 09:11:23 - >Received: (qmail 84462 invoked from network); 16 Nov 2001 09:11:23 - >From cocoon-users-return-25809-jackhirasawa Fri, 16 Nov 2001 01:13:38 -0800 >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >Precedence: bulk >list-help: <mailto:[EMAIL PROTECTED]> >list-unsubscribe: <mailt
RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Title: RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hello Jack, Your instructions really helped. We now have the problem: when we access the URL, it seems that it is redirected to a welcome page. We have the message that this ressource is not found. Any idea about that? We can see that it is now running (from the traces) but the welcome page/ressource is not found. Is there something else that has to be defined? Many thanks Gilles -Original Message- From: Jack Hirasawa [mailto:[EMAIL PROTECTED]] Sent: vendredi, 16. novembre 2001 15:51 To: [EMAIL PROTECTED] Subject: Re: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hi Gilles, Have you checked the mail archives? You should check there first before asking (they are in there). But enough nagging, to make your life easier here's the instructions again for Cocoon2... 1) If there's a Cocoon-2.0rc1\build directory, delete it 2) set JAVA_HOME=c:\WebSphere\AppServer\jdk 3) .\build.bat -Dinclude.webapp.libs=yes -Dinstall.war=c:\WebSphere\AppServer\hosts\default_host\cocoon webapp 4) Fire Up the Websphere admin server and the Admin console 5) Go to the Servlet Container and put it in Servlet 2.2 full compliance mode 6) Deploy the WAR file in c:\Cocoon-2.0rc1\build\cocoon (use Convert a WAR File) 7) Update the Server Command Line Arguments: -Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser -classpath C:\Cocoon-2.0rc1\lib\xerces_1_4_3.jar;C:\Cocoon-2.0rc1\lib\cocoon-2.0rc1.jar;C:\Cocoon-2.0rc1\lib\velocity-1.1.jar;C:\Cocoon-2.0rc1\lib\servlet_2_2.jar;C:\Cocoon-2.0rc1\lib\maybeupload.jar;C:\Cocoon-2.0rc1\lib\batik-libs.jar;C:\Cocoon-2.0rc1\lib\ant_1_4.jar;C:\Cocoon-2.0rc1\lib\xalan-2.2.0-dev.jar;C:\Cocoon-2.0rc1\lib\logkit-1.0b5.jar;C:\Cocoon-2.0rc1\lib\fop-0_20_1-dev.jar;C:\Cocoon-2.0rc1\lib\resolver.jar;C:\Cocoon-2.0rc1\lib\ant_1_4-optional.jar;C:\Cocoon-2.0rc1\lib\avalon-framework-4.0.jar;C:\Cocoon-2.0rc1\lib\jakarta-regexp-1.2.jar;C:\Cocoon-2.0rc1\lib\dom2.jar;C:\Cocoon-2.0rc1\lib\rhino.jar;C:\Cocoon-2.0rc1\lib\xt.jar;C:\Cocoon-2.0rc1\lib\hsqldb-1.61.jar;C:\Cocoon-2.0rc1\lib\avalon-excalibur-4.0.jar;C:\Cocoon-2.0rc1\lib\Tidy.jar;C:\Cocoon-2.0rc1\lib\stylebook-1.0-b3_xalan-2.jar;C:\Cocoon-2.0rc1\lib\junit.jar;C:\Cocoon-2.0rc1\lib\jimi-1.0.jar;C:\Cocoon-2.0rc1\lib\jstyle.jar;C:\Cocoo n-2.0rc1\lib\bsf.jar;C:/WebSphere/AppServer/jdk/lib/tools.jar;c:\WebSphere\AppServer\hosts\default_host\cocoon\servlets\cocoon-2.0rc1.jar 8) Select the Servlet Cocoon2 and Add a Servlet Web Path /cocoon/* 9) On the advanced tab add the following init parameters org.apache.cocoon.component.parser.Parser=org.apache.cocoon.components.parser.XercesParser force-load=com.ibm.servlet.classloader.Handler classpath-attribute=com.ibm.websphere.servlet.application.classpath 10) In the Web directory of the Webapp edit cocoon.xconf and move the parser statement out of the comment block 11) Copy the WEB-INF directory from the web directory to the servlets directory 12) Copy the cocoon.xconf file from the web directory to the servlets directory 12) Shut down the Admin console 13) Shut down the Admin server and restart it 14) Restart the admin console 15) Start the server For step 7) you should really probably use the jar files that get deployed in the servlets directory instead of the ones in the build directory. Hope this helps. If you're trying to get cocoon 1.8.2 working, check the archives, I got it working a while ago and I used the tips in the archives. Jack >From: "Ducret, Gilles (CH)" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 >Date: Fri, 16 Nov 2001 10:10:00 +0100 >MIME-Version: 1.0 >Received: from [64.125.133.20] by hotmail.com (3.2) with ESMTP id >MHotMailBDBE23B1009940042A18407D851404FD0; Fri, 16 Nov 2001 01:13:23 -0800 >Received: (qmail 84477 invoked by uid 500); 16 Nov 2001 09:11:23 - >Received: (qmail 84462 invoked from network); 16 Nov 2001 09:11:23 - >From cocoon-users-return-25809-jackhirasawa Fri, 16 Nov 2001 01:13:38 -0800 >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >Precedence: bulk >list-help: <mailto:[EMAIL PROTECTED]> >list-unsubscribe: <mailto:[EMAIL PROTECTED]> >list-post: <mailto:[EMAIL PROTECTED]> >Delivered-To: mailing list [EMAIL PROTECTED] >Message-ID: ><[EMAIL PROTECTED]> >X-Mailer: Internet Mail Service (5.5.2650.21) >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > >Hello, > >We are experiencing a lot of problem on installing Cocoon on Websphere 3.5. > >If we don't use the Websphere 3.4.2 of websphere, we have the following >behaviour: > - Cocoon 1.8 works fine > - Cocoon 2.0 doesn't work. Cocoon servlet throws a >ClassCastEx
RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Title: RE: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Sorry i had not found it in the archive. I will try many thanks for your help -Original Message- From: Jack Hirasawa [mailto:[EMAIL PROTECTED]] Sent: vendredi, 16. novembre 2001 15:51 To: [EMAIL PROTECTED] Subject: Re: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hi Gilles, Have you checked the mail archives? You should check there first before asking (they are in there). But enough nagging, to make your life easier here's the instructions again for Cocoon2... 1) If there's a Cocoon-2.0rc1\build directory, delete it 2) set JAVA_HOME=c:\WebSphere\AppServer\jdk 3) .\build.bat -Dinclude.webapp.libs=yes -Dinstall.war=c:\WebSphere\AppServer\hosts\default_host\cocoon webapp 4) Fire Up the Websphere admin server and the Admin console 5) Go to the Servlet Container and put it in Servlet 2.2 full compliance mode 6) Deploy the WAR file in c:\Cocoon-2.0rc1\build\cocoon (use Convert a WAR File) 7) Update the Server Command Line Arguments: -Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser -classpath C:\Cocoon-2.0rc1\lib\xerces_1_4_3.jar;C:\Cocoon-2.0rc1\lib\cocoon-2.0rc1.jar;C:\Cocoon-2.0rc1\lib\velocity-1.1.jar;C:\Cocoon-2.0rc1\lib\servlet_2_2.jar;C:\Cocoon-2.0rc1\lib\maybeupload.jar;C:\Cocoon-2.0rc1\lib\batik-libs.jar;C:\Cocoon-2.0rc1\lib\ant_1_4.jar;C:\Cocoon-2.0rc1\lib\xalan-2.2.0-dev.jar;C:\Cocoon-2.0rc1\lib\logkit-1.0b5.jar;C:\Cocoon-2.0rc1\lib\fop-0_20_1-dev.jar;C:\Cocoon-2.0rc1\lib\resolver.jar;C:\Cocoon-2.0rc1\lib\ant_1_4-optional.jar;C:\Cocoon-2.0rc1\lib\avalon-framework-4.0.jar;C:\Cocoon-2.0rc1\lib\jakarta-regexp-1.2.jar;C:\Cocoon-2.0rc1\lib\dom2.jar;C:\Cocoon-2.0rc1\lib\rhino.jar;C:\Cocoon-2.0rc1\lib\xt.jar;C:\Cocoon-2.0rc1\lib\hsqldb-1.61.jar;C:\Cocoon-2.0rc1\lib\avalon-excalibur-4.0.jar;C:\Cocoon-2.0rc1\lib\Tidy.jar;C:\Cocoon-2.0rc1\lib\stylebook-1.0-b3_xalan-2.jar;C:\Cocoon-2.0rc1\lib\junit.jar;C:\Cocoon-2.0rc1\lib\jimi-1.0.jar;C:\Cocoon-2.0rc1\lib\jstyle.jar;C:\Cocoo n-2.0rc1\lib\bsf.jar;C:/WebSphere/AppServer/jdk/lib/tools.jar;c:\WebSphere\AppServer\hosts\default_host\cocoon\servlets\cocoon-2.0rc1.jar 8) Select the Servlet Cocoon2 and Add a Servlet Web Path /cocoon/* 9) On the advanced tab add the following init parameters org.apache.cocoon.component.parser.Parser=org.apache.cocoon.components.parser.XercesParser force-load=com.ibm.servlet.classloader.Handler classpath-attribute=com.ibm.websphere.servlet.application.classpath 10) In the Web directory of the Webapp edit cocoon.xconf and move the parser statement out of the comment block 11) Copy the WEB-INF directory from the web directory to the servlets directory 12) Copy the cocoon.xconf file from the web directory to the servlets directory 12) Shut down the Admin console 13) Shut down the Admin server and restart it 14) Restart the admin console 15) Start the server For step 7) you should really probably use the jar files that get deployed in the servlets directory instead of the ones in the build directory. Hope this helps. If you're trying to get cocoon 1.8.2 working, check the archives, I got it working a while ago and I used the tips in the archives. Jack >From: "Ducret, Gilles (CH)" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 >Date: Fri, 16 Nov 2001 10:10:00 +0100 >MIME-Version: 1.0 >Received: from [64.125.133.20] by hotmail.com (3.2) with ESMTP id >MHotMailBDBE23B1009940042A18407D851404FD0; Fri, 16 Nov 2001 01:13:23 -0800 >Received: (qmail 84477 invoked by uid 500); 16 Nov 2001 09:11:23 - >Received: (qmail 84462 invoked from network); 16 Nov 2001 09:11:23 - >From cocoon-users-return-25809-jackhirasawa Fri, 16 Nov 2001 01:13:38 -0800 >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >Precedence: bulk >list-help: <mailto:[EMAIL PROTECTED]> >list-unsubscribe: <mailto:[EMAIL PROTECTED]> >list-post: <mailto:[EMAIL PROTECTED]> >Delivered-To: mailing list [EMAIL PROTECTED] >Message-ID: ><[EMAIL PROTECTED]> >X-Mailer: Internet Mail Service (5.5.2650.21) >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > >Hello, > >We are experiencing a lot of problem on installing Cocoon on Websphere 3.5. > >If we don't use the Websphere 3.4.2 of websphere, we have the following >behaviour: > - Cocoon 1.8 works fine > - Cocoon 2.0 doesn't work. Cocoon servlet throws a >ClassCastException > >Unfortunately, in our live system the Websphere 3.4.2 fixpack is installed. > >With Websphere 3,5, fixpack 3.4.2 > - Cocoon 1.8 doesn't work > . Cocoon 2.0 still throws a class cast exception > >Any idea how to solve this? > >Any help would be very much appreciated
Re: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Hi Gilles, Have you checked the mail archives? You should check there first before asking (they are in there). But enough nagging, to make your life easier here's the instructions again for Cocoon2... 1) If there's a Cocoon-2.0rc1\build directory, delete it 2) set JAVA_HOME=c:\WebSphere\AppServer\jdk 3) .\build.bat -Dinclude.webapp.libs=yes -Dinstall.war=c:\WebSphere\AppServer\hosts\default_host\cocoon webapp 4) Fire Up the Websphere admin server and the Admin console 5) Go to the Servlet Container and put it in Servlet 2.2 full compliance mode 6) Deploy the WAR file in c:\Cocoon-2.0rc1\build\cocoon (use Convert a WAR File) 7) Update the Server Command Line Arguments: -Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser -classpath C:\Cocoon-2.0rc1\lib\xerces_1_4_3.jar;C:\Cocoon-2.0rc1\lib\cocoon-2.0rc1.jar;C:\Cocoon-2.0rc1\lib\velocity-1.1.jar;C:\Cocoon-2.0rc1\lib\servlet_2_2.jar;C:\Cocoon-2.0rc1\lib\maybeupload.jar;C:\Cocoon-2.0rc1\lib\batik-libs.jar;C:\Cocoon-2.0rc1\lib\ant_1_4.jar;C:\Cocoon-2.0rc1\lib\xalan-2.2.0-dev.jar;C:\Cocoon-2.0rc1\lib\logkit-1.0b5.jar;C:\Cocoon-2.0rc1\lib\fop-0_20_1-dev.jar;C:\Cocoon-2.0rc1\lib\resolver.jar;C:\Cocoon-2.0rc1\lib\ant_1_4-optional.jar;C:\Cocoon-2.0rc1\lib\avalon-framework-4.0.jar;C:\Cocoon-2.0rc1\lib\jakarta-regexp-1.2.jar;C:\Cocoon-2.0rc1\lib\dom2.jar;C:\Cocoon-2.0rc1\lib\rhino.jar;C:\Cocoon-2.0rc1\lib\xt.jar;C:\Cocoon-2.0rc1\lib\hsqldb-1.61.jar;C:\Cocoon-2.0rc1\lib\avalon-excalibur-4.0.jar;C:\Cocoon-2.0rc1\lib\Tidy.jar;C:\Cocoon-2.0rc1\lib\stylebook-1.0-b3_xalan-2.jar;C:\Cocoon-2.0rc1\lib\junit.jar;C:\Cocoon-2.0rc1\lib\jimi-1.0.jar;C:\Cocoon-2.0rc1\lib\jstyle.jar;C:\Cocoo n-2.0rc1\lib\bsf.jar;C:/WebSphere/AppServer/jdk/lib/tools.jar;c:\WebSphere\AppServer\hosts\default_host\cocoon\servlets\cocoon-2.0rc1.jar 8) Select the Servlet Cocoon2 and Add a Servlet Web Path /cocoon/* 9) On the advanced tab add the following init parameters org.apache.cocoon.component.parser.Parser=org.apache.cocoon.components.parser.XercesParser force-load=com.ibm.servlet.classloader.Handler classpath-attribute=com.ibm.websphere.servlet.application.classpath 10) In the Web directory of the Webapp edit cocoon.xconf and move the parser statement out of the comment block 11) Copy the WEB-INF directory from the web directory to the servlets directory 12) Copy the cocoon.xconf file from the web directory to the servlets directory 12) Shut down the Admin console 13) Shut down the Admin server and restart it 14) Restart the admin console 15) Start the server For step 7) you should really probably use the jar files that get deployed in the servlets directory instead of the ones in the build directory. Hope this helps. If you're trying to get cocoon 1.8.2 working, check the archives, I got it working a while ago and I used the tips in the archives. Jack >From: "Ducret, Gilles (CH)" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 >Date: Fri, 16 Nov 2001 10:10:00 +0100 >MIME-Version: 1.0 >Received: from [64.125.133.20] by hotmail.com (3.2) with ESMTP id >MHotMailBDBE23B1009940042A18407D851404FD0; Fri, 16 Nov 2001 01:13:23 -0800 >Received: (qmail 84477 invoked by uid 500); 16 Nov 2001 09:11:23 - >Received: (qmail 84462 invoked from network); 16 Nov 2001 09:11:23 - >From cocoon-users-return-25809-jackhirasawa Fri, 16 Nov 2001 01:13:38 -0800 >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >Precedence: bulk >list-help: <mailto:[EMAIL PROTECTED]> >list-unsubscribe: <mailto:[EMAIL PROTECTED]> >list-post: <mailto:[EMAIL PROTECTED]> >Delivered-To: mailing list [EMAIL PROTECTED] >Message-ID: ><[EMAIL PROTECTED]> >X-Mailer: Internet Mail Service (5.5.2650.21) >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > >Hello, > >We are experiencing a lot of problem on installing Cocoon on Websphere 3.5. > >If we don't use the Websphere 3.4.2 of websphere, we have the following >behaviour: > - Cocoon 1.8 works fine > - Cocoon 2.0 doesn't work. Cocoon servlet throws a >ClassCastException > >Unfortunately, in our live system the Websphere 3.4.2 fixpack is installed. > >With Websphere 3,5, fixpack 3.4.2 > - Cocoon 1.8 doesn't work > . Cocoon 2.0 still throws a class cast exception > >Any idea how to solve this? > >Any help would be very much appreciated > > >Gilles Ducret >Wealth Management Division >IT Architect >Lloyds TSB Bank >Tel: + 41 22 307 31 50 >Mob: +41 79 217 21 41 > > > >** >This
Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2
Title: Cocoon and WEBSPHERE 3.5 Fixpack 3.4.2 Hello, We are experiencing a lot of problem on installing Cocoon on Websphere 3.5. If we don't use the Websphere 3.4.2 of websphere, we have the following behaviour: - Cocoon 1.8 works fine - Cocoon 2.0 doesn't work. Cocoon servlet throws a ClassCastException Unfortunately, in our live system the Websphere 3.4.2 fixpack is installed. With Websphere 3,5, fixpack 3.4.2 - Cocoon 1.8 doesn't work . Cocoon 2.0 still throws a class cast exception Any idea how to solve this? Any help would be very much appreciated Gilles Ducret Wealth Management Division IT Architect Lloyds TSB Bank Tel: + 41 22 307 31 50 Mob: +41 79 217 21 41 ** This E-mail and any files transmitted with it are confidential and intended for the exclusive use of the addressee(s) only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender immediately. **
