You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Philip Aston <pa...@bea.com> on 2000/06/16 09:30:24 UTC
Cocoon 1.7.4. vs BEA WebLogic Server
I've been playing with using Cocoon 1.7.4 in conjunction with BEA
WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
of this to the installation guide. You might also like to add a
success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
1.2.2.)
WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
recipe:
- Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
distribution) to your CLASSPATH. (See below). If you're using Java
2, you should also add the tools.jar file from the JDK distribution
to your CLASSPATH.
- Create a new subdirectory tree of your WLS run time directory
"cocoonwar/WEB-INF" and copy the default web.xml file (from the
src directory of the distribution) there.
- Copy the cocoon.properties from the conf directory of the
distribution to cocoonwar/WEB-INF and updated the web.xml file to
refer to it.
- Copy the samples directory from the distribution to cocoonwar
- Map the web application into the WLS URI name space by adding the
following line to your weblogic.properties file:
weblogic.httpd.webApp.cocoon=cocoonwar
Start WLS, point your browser at
"http://localhost:7001/cocoon/samples/index.xml" and away you go.
Classpaths and XSP:
To support hot deployment of EJB's and Servlets, WebLogic Server
uses its own class loader with its own classpath (the "WebLogic
classpath"). Normally you'd put all the WebLogic Server container
code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
Server can start up) and add all your application code (stuff that
needs to be able to be redeployable) to the WebLogic classpath.
Cocoon is effectively "container" code, and the XSP processor uses
dynamic classloading which only understands the Java CLASSPATH, so
you should put all of the Cocoon jars in CLASSPATH.
The big problem with this is that you can't use any code that loads
from the WebLogic classpath within XSP's. This includes all of the
WebLogic API, so is a PITA. To overcome this, either the way Cocoon
loads classes needs to be modified (Stefano, is this easy?), or the
WebLogic Server class loader needs to be disabled (in which case you
have to be willing to live without hot redeployment).
To disable the WebLogic class loader, put your application classes,
the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
Java command at the end of you WebLogic start script.
- Phil
This is not an official BEA response. Please do not send me unrelated
WebLogic support questions - I am unable to answer them. Instead
please use the BEA developer newsgroups - see
http://developer.bea.com, or contact BEA support.
-------------------------------------------
Philip Aston - Senior Consultant
BEA Professional Services (Northern Europe)
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Russell Castagnaro <ru...@synctank.com>.
I second that!
Kevin Yancy wrote:
> Hi Phillip
>
> Yee Ha! With the info you provided I was finally able to get XSP working
> under WebLogic 5.1 !!! I really appreciate your insights.
>
> thanx a lot!
> Kevin
>
> Philip Aston wrote:
>
> > I've been playing with using Cocoon 1.7.4 in conjunction with BEA
> > WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
> > of this to the installation guide. You might also like to add a
> > success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
> > 1.2.2.)
> >
> > WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
> > recipe:
> > - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
> > distribution) to your CLASSPATH. (See below). If you're using Java
> > 2, you should also add the tools.jar file from the JDK distribution
> > to your CLASSPATH.
> > - Create a new subdirectory tree of your WLS run time directory
> > "cocoonwar/WEB-INF" and copy the default web.xml file (from the
> > src directory of the distribution) there.
> > - Copy the cocoon.properties from the conf directory of the
> > distribution to cocoonwar/WEB-INF and updated the web.xml file to
> > refer to it.
> > - Copy the samples directory from the distribution to cocoonwar
> > - Map the web application into the WLS URI name space by adding the
> > following line to your weblogic.properties file:
> > weblogic.httpd.webApp.cocoon=cocoonwar
> >
> > Start WLS, point your browser at
> > "http://localhost:7001/cocoon/samples/index.xml" and away you go.
> >
> > Classpaths and XSP:
> >
> > To support hot deployment of EJB's and Servlets, WebLogic Server
> > uses its own class loader with its own classpath (the "WebLogic
> > classpath"). Normally you'd put all the WebLogic Server container
> > code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
> > Server can start up) and add all your application code (stuff that
> > needs to be able to be redeployable) to the WebLogic classpath.
> >
> > Cocoon is effectively "container" code, and the XSP processor uses
> > dynamic classloading which only understands the Java CLASSPATH, so
> > you should put all of the Cocoon jars in CLASSPATH.
> >
> > The big problem with this is that you can't use any code that loads
> > from the WebLogic classpath within XSP's. This includes all of the
> > WebLogic API, so is a PITA. To overcome this, either the way Cocoon
> > loads classes needs to be modified (Stefano, is this easy?), or the
> > WebLogic Server class loader needs to be disabled (in which case you
> > have to be willing to live without hot redeployment).
> >
> > To disable the WebLogic class loader, put your application classes,
> > the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
> > CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
> > Java command at the end of you WebLogic start script.
> >
> > - Phil
> >
> > This is not an official BEA response. Please do not send me unrelated
> > WebLogic support questions - I am unable to answer them. Instead
> > please use the BEA developer newsgroups - see
> > http://developer.bea.com, or contact BEA support.
> >
> > -------------------------------------------
> > Philip Aston - Senior Consultant
> > BEA Professional Services (Northern Europe)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> > For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
> --
> Kevin Yancy
> --
> kyancy@geobot.com
> http://www.geobot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Hope to see you at my presentation, "Making the Most of XML, XSL and Server-Side
Processing"
at XML DevCon 2000, June 25-28, 2000.
Russell Castagnaro
Chief Mentor
SyncTank Solutions
http://www.synctank.com
Earth is the cradle of mankind; one does not remain in the cradle forever
-Tsiolkovsky
Re: (STEPHANO PLEASE READ THIS) RE: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Stefano Mazzocchi <st...@apache.org>.
Pat Laplante wrote:
>
> Spiacente!
Nessun problema :)
I just have to remind people about this or pretty soon nobody will write
it right...
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
RE: (STEPHANO PLEASE READ THIS) RE: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Pat Laplante <pl...@vanteon.com>.
Spiacente!
-----Original Message-----
From: Stefano Mazzocchi [mailto:stefano@apache.org]
Sent: Wednesday, June 21, 2000 6:48 AM
To: cocoon-users@xml.apache.org
Subject: Re: (STEPHANO PLEASE READ THIS) RE: Cocoon 1.7.4. vs BEA
WebLogic Server
My name is "Stefano" BTW...
Pat Laplante wrote:
>
> Hi there....
>
> I had the same problem where weblogic was running in a static class
loading mode instead of dynamic.
>
> I was able to fix it by modifying the cocoon XSPJavaProcessor.java file.
Instead of using java.class.path I am using
> cocoon.class.path. Then I recompiled the file and put in cocoon.jar.
>
> Now when I start weblogic, I put all the weblogic stuff in
weblogic.class.path, all the cocoon stuff in cocoon.class.path and the
> boot stuff of weblogic in javaclasspath.
>
> java <someoptions> -classpath <bootstuff> -Dweblogic.class.path=<weblogic
stuff> -Dcocoon.class.path=<cocoon stuff>. weblogic run
> in dynamic class loading mode and cocoon works fine.
>
> I honestly that cocoon should not rely on the java classpath but should
rely on some other class path like I did.
Well, it would work for Weblogic and break JServ... at least in
automatic operation.
> Stephano... what do you think?
The classpath problem is a serious one but for Cocoon2 we have Java2
capabilities and this should save us from all these hacks since we can
use our own classloaders with no problems.
I don't want to mess around with Cocoon1 classpaths just now... I'd
rather concentrate on C2 stuff.
But that's only my personal opinion....
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: (STEPHANO PLEASE READ THIS) RE: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Stefano Mazzocchi <st...@apache.org>.
My name is "Stefano" BTW...
Pat Laplante wrote:
>
> Hi there....
>
> I had the same problem where weblogic was running in a static class loading mode instead of dynamic.
>
> I was able to fix it by modifying the cocoon XSPJavaProcessor.java file. Instead of using java.class.path I am using
> cocoon.class.path. Then I recompiled the file and put in cocoon.jar.
>
> Now when I start weblogic, I put all the weblogic stuff in weblogic.class.path, all the cocoon stuff in cocoon.class.path and the
> boot stuff of weblogic in javaclasspath.
>
> java <someoptions> -classpath <bootstuff> -Dweblogic.class.path=<weblogic stuff> -Dcocoon.class.path=<cocoon stuff>. weblogic run
> in dynamic class loading mode and cocoon works fine.
>
> I honestly that cocoon should not rely on the java classpath but should rely on some other class path like I did.
Well, it would work for Weblogic and break JServ... at least in
automatic operation.
> Stephano... what do you think?
The classpath problem is a serious one but for Cocoon2 we have Java2
capabilities and this should save us from all these hacks since we can
use our own classloaders with no problems.
I don't want to mess around with Cocoon1 classpaths just now... I'd
rather concentrate on C2 stuff.
But that's only my personal opinion....
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
(STEPHANO PLEASE READ THIS) RE: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Pat Laplante <pl...@vanteon.com>.
Hi there....
I had the same problem where weblogic was running in a static class loading mode instead of dynamic.
I was able to fix it by modifying the cocoon XSPJavaProcessor.java file. Instead of using java.class.path I am using
cocoon.class.path. Then I recompiled the file and put in cocoon.jar.
Now when I start weblogic, I put all the weblogic stuff in weblogic.class.path, all the cocoon stuff in cocoon.class.path and the
boot stuff of weblogic in javaclasspath.
java <someoptions> -classpath <bootstuff> -Dweblogic.class.path=<weblogic stuff> -Dcocoon.class.path=<cocoon stuff>. weblogic run
in dynamic class loading mode and cocoon works fine.
I honestly that cocoon should not rely on the java classpath but should rely on some other class path like I did.
Stephano... what do you think?
-----Original Message-----
From: Kevin Yancy [mailto:kyancy@geobot.com]
Sent: Tuesday, June 20, 2000 8:29 PM
To: cocoon-users@xml.apache.org
Subject: Re: Cocoon 1.7.4. vs BEA WebLogic Server
Hi Phillip
Yee Ha! With the info you provided I was finally able to get XSP working
under WebLogic 5.1 !!! I really appreciate your insights.
thanx a lot!
Kevin
Philip Aston wrote:
> I've been playing with using Cocoon 1.7.4 in conjunction with BEA
> WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
> of this to the installation guide. You might also like to add a
> success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
> 1.2.2.)
>
> WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
> recipe:
> - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
> distribution) to your CLASSPATH. (See below). If you're using Java
> 2, you should also add the tools.jar file from the JDK distribution
> to your CLASSPATH.
> - Create a new subdirectory tree of your WLS run time directory
> "cocoonwar/WEB-INF" and copy the default web.xml file (from the
> src directory of the distribution) there.
> - Copy the cocoon.properties from the conf directory of the
> distribution to cocoonwar/WEB-INF and updated the web.xml file to
> refer to it.
> - Copy the samples directory from the distribution to cocoonwar
> - Map the web application into the WLS URI name space by adding the
> following line to your weblogic.properties file:
> weblogic.httpd.webApp.cocoon=cocoonwar
>
> Start WLS, point your browser at
> "http://localhost:7001/cocoon/samples/index.xml" and away you go.
>
> Classpaths and XSP:
>
> To support hot deployment of EJB's and Servlets, WebLogic Server
> uses its own class loader with its own classpath (the "WebLogic
> classpath"). Normally you'd put all the WebLogic Server container
> code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
> Server can start up) and add all your application code (stuff that
> needs to be able to be redeployable) to the WebLogic classpath.
>
> Cocoon is effectively "container" code, and the XSP processor uses
> dynamic classloading which only understands the Java CLASSPATH, so
> you should put all of the Cocoon jars in CLASSPATH.
>
> The big problem with this is that you can't use any code that loads
> from the WebLogic classpath within XSP's. This includes all of the
> WebLogic API, so is a PITA. To overcome this, either the way Cocoon
> loads classes needs to be modified (Stefano, is this easy?), or the
> WebLogic Server class loader needs to be disabled (in which case you
> have to be willing to live without hot redeployment).
>
> To disable the WebLogic class loader, put your application classes,
> the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
> CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
> Java command at the end of you WebLogic start script.
>
> - Phil
>
> This is not an official BEA response. Please do not send me unrelated
> WebLogic support questions - I am unable to answer them. Instead
> please use the BEA developer newsgroups - see
> http://developer.bea.com, or contact BEA support.
>
> -------------------------------------------
> Philip Aston - Senior Consultant
> BEA Professional Services (Northern Europe)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Kevin Yancy
--
kyancy@geobot.com
http://www.geobot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Kevin Yancy <ky...@geobot.com>.
Hi Phillip
Yee Ha! With the info you provided I was finally able to get XSP working
under WebLogic 5.1 !!! I really appreciate your insights.
thanx a lot!
Kevin
Philip Aston wrote:
> I've been playing with using Cocoon 1.7.4 in conjunction with BEA
> WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
> of this to the installation guide. You might also like to add a
> success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
> 1.2.2.)
>
> WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
> recipe:
> - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
> distribution) to your CLASSPATH. (See below). If you're using Java
> 2, you should also add the tools.jar file from the JDK distribution
> to your CLASSPATH.
> - Create a new subdirectory tree of your WLS run time directory
> "cocoonwar/WEB-INF" and copy the default web.xml file (from the
> src directory of the distribution) there.
> - Copy the cocoon.properties from the conf directory of the
> distribution to cocoonwar/WEB-INF and updated the web.xml file to
> refer to it.
> - Copy the samples directory from the distribution to cocoonwar
> - Map the web application into the WLS URI name space by adding the
> following line to your weblogic.properties file:
> weblogic.httpd.webApp.cocoon=cocoonwar
>
> Start WLS, point your browser at
> "http://localhost:7001/cocoon/samples/index.xml" and away you go.
>
> Classpaths and XSP:
>
> To support hot deployment of EJB's and Servlets, WebLogic Server
> uses its own class loader with its own classpath (the "WebLogic
> classpath"). Normally you'd put all the WebLogic Server container
> code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
> Server can start up) and add all your application code (stuff that
> needs to be able to be redeployable) to the WebLogic classpath.
>
> Cocoon is effectively "container" code, and the XSP processor uses
> dynamic classloading which only understands the Java CLASSPATH, so
> you should put all of the Cocoon jars in CLASSPATH.
>
> The big problem with this is that you can't use any code that loads
> from the WebLogic classpath within XSP's. This includes all of the
> WebLogic API, so is a PITA. To overcome this, either the way Cocoon
> loads classes needs to be modified (Stefano, is this easy?), or the
> WebLogic Server class loader needs to be disabled (in which case you
> have to be willing to live without hot redeployment).
>
> To disable the WebLogic class loader, put your application classes,
> the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
> CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
> Java command at the end of you WebLogic start script.
>
> - Phil
>
> This is not an official BEA response. Please do not send me unrelated
> WebLogic support questions - I am unable to answer them. Instead
> please use the BEA developer newsgroups - see
> http://developer.bea.com, or contact BEA support.
>
> -------------------------------------------
> Philip Aston - Senior Consultant
> BEA Professional Services (Northern Europe)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Kevin Yancy
--
kyancy@geobot.com
http://www.geobot.com
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Russell Castagnaro <ru...@synctank.com>.
FYI-
This configuration doesn't support hot deploying EJB's or XSP as far as I can
tell.
-rrc
Stefano Mazzocchi wrote:
> Philip Aston wrote:
> >
> > I've been playing with using Cocoon 1.7.4 in conjunction with BEA
> > WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
> > of this to the installation guide. You might also like to add a
> > success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
> > 1.2.2.)
>
> Will do, thanks.
>
> > WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
> > recipe:
> > - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
> > distribution) to your CLASSPATH. (See below). If you're using Java
> > 2, you should also add the tools.jar file from the JDK distribution
> > to your CLASSPATH.
> > - Create a new subdirectory tree of your WLS run time directory
> > "cocoonwar/WEB-INF" and copy the default web.xml file (from the
> > src directory of the distribution) there.
> > - Copy the cocoon.properties from the conf directory of the
> > distribution to cocoonwar/WEB-INF and updated the web.xml file to
> > refer to it.
> > - Copy the samples directory from the distribution to cocoonwar
> > - Map the web application into the WLS URI name space by adding the
> > following line to your weblogic.properties file:
> > weblogic.httpd.webApp.cocoon=cocoonwar
> >
> > Start WLS, point your browser at
> > "http://localhost:7001/cocoon/samples/index.xml" and away you go.
> >
> > Classpaths and XSP:
> >
> > To support hot deployment of EJB's and Servlets, WebLogic Server
> > uses its own class loader with its own classpath (the "WebLogic
> > classpath"). Normally you'd put all the WebLogic Server container
> > code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
> > Server can start up) and add all your application code (stuff that
> > needs to be able to be redeployable) to the WebLogic classpath.
> >
> > Cocoon is effectively "container" code, and the XSP processor uses
> > dynamic classloading which only understands the Java CLASSPATH, so
> > you should put all of the Cocoon jars in CLASSPATH.
> >
> > The big problem with this is that you can't use any code that loads
> > from the WebLogic classpath within XSP's. This includes all of the
> > WebLogic API, so is a PITA. To overcome this, either the way Cocoon
> > loads classes needs to be modified (Stefano, is this easy?), or the
> > WebLogic Server class loader needs to be disabled (in which case you
> > have to be willing to live without hot redeployment).
> >
> > To disable the WebLogic class loader, put your application classes,
> > the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
> > CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
> > Java command at the end of you WebLogic start script.
> >
> > - Phil
> >
> > This is not an official BEA response. Please do not send me unrelated
> > WebLogic support questions - I am unable to answer them. Instead
> > please use the BEA developer newsgroups - see
> > http://developer.bea.com, or contact BEA support.
> >
> > -------------------------------------------
> > Philip Aston - Senior Consultant
> > BEA Professional Services (Northern Europe)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> > For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
> Missed us in Orlando? Make it up with ApacheCON Europe in London!
> ------------------------- http://ApacheCon.Com ---------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Hope to see you at my presentation, "Making the Most of XML, XSL and Server-Side
Processing"
at XML DevCon 2000, June 25-28, 2000.
Russell Castagnaro
Chief Mentor
SyncTank Solutions
http://www.synctank.com
Earth is the cradle of mankind; one does not remain in the cradle forever
-Tsiolkovsky
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Stefano Mazzocchi <st...@apache.org>.
Philip Aston wrote:
>
> I've been playing with using Cocoon 1.7.4 in conjunction with BEA
> WebLogic Server 5.1. (Stefano and folks, feel free to add any or all
> of this to the installation guide. You might also like to add a
> success report for MS NT 4.0 SP4, BEA WebLogic Server 5.1 SP3, JDK
> 1.2.2.)
Will do, thanks.
> WLS 5.1 implements Servlet 2.2. so it plugs in easily. Here's a quick
> recipe:
> - Add the xerces, xalan, fop, servlet, and cocoon JAR files (from the
> distribution) to your CLASSPATH. (See below). If you're using Java
> 2, you should also add the tools.jar file from the JDK distribution
> to your CLASSPATH.
> - Create a new subdirectory tree of your WLS run time directory
> "cocoonwar/WEB-INF" and copy the default web.xml file (from the
> src directory of the distribution) there.
> - Copy the cocoon.properties from the conf directory of the
> distribution to cocoonwar/WEB-INF and updated the web.xml file to
> refer to it.
> - Copy the samples directory from the distribution to cocoonwar
> - Map the web application into the WLS URI name space by adding the
> following line to your weblogic.properties file:
> weblogic.httpd.webApp.cocoon=cocoonwar
>
> Start WLS, point your browser at
> "http://localhost:7001/cocoon/samples/index.xml" and away you go.
>
> Classpaths and XSP:
>
> To support hot deployment of EJB's and Servlets, WebLogic Server
> uses its own class loader with its own classpath (the "WebLogic
> classpath"). Normally you'd put all the WebLogic Server container
> code, JDBC drivers, etc. in your Java CLASSPATH (so that WebLogic
> Server can start up) and add all your application code (stuff that
> needs to be able to be redeployable) to the WebLogic classpath.
>
> Cocoon is effectively "container" code, and the XSP processor uses
> dynamic classloading which only understands the Java CLASSPATH, so
> you should put all of the Cocoon jars in CLASSPATH.
>
> The big problem with this is that you can't use any code that loads
> from the WebLogic classpath within XSP's. This includes all of the
> WebLogic API, so is a PITA. To overcome this, either the way Cocoon
> loads classes needs to be modified (Stefano, is this easy?), or the
> WebLogic Server class loader needs to be disabled (in which case you
> have to be willing to live without hot redeployment).
>
> To disable the WebLogic class loader, put your application classes,
> the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
> CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
> Java command at the end of you WebLogic start script.
>
> - Phil
>
> This is not an official BEA response. Please do not send me unrelated
> WebLogic support questions - I am unable to answer them. Instead
> please use the BEA developer newsgroups - see
> http://developer.bea.com, or contact BEA support.
>
> -------------------------------------------
> Philip Aston - Senior Consultant
> BEA Professional Services (Northern Europe)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Stefano Mazzocchi <st...@apache.org>.
Philip Aston wrote:
>
> Thanks to whoever added my WebLogic Server 5.1 HOWTO to
> http://xml.apache.org/cocoon/install.html.
>
> Unfortunately, the page now contains two sections labelled "Installing
> Cocoon on BEA WebLogic". To be correct, the first section should be
> titled "Installing Cocoon on BEA WebLogic Server 4.5.1", and the
> second section "Installing Cocoon on BEA WebLogic Server 5.1".
>
> You might also like to add the following note to the end of the second
> section:
>
> "The above will also work for installing Cocoon in the BEA WebLogic
> Enterprise 5.1 J-Engine."
>
> Thanks,
Will do right away, thanks.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: Cocoon 1.7.4. vs BEA WebLogic Server
Posted by Philip Aston <pa...@bea.com>.
Thanks to whoever added my WebLogic Server 5.1 HOWTO to
http://xml.apache.org/cocoon/install.html.
Unfortunately, the page now contains two sections labelled "Installing
Cocoon on BEA WebLogic". To be correct, the first section should be
titled "Installing Cocoon on BEA WebLogic Server 4.5.1", and the
second section "Installing Cocoon on BEA WebLogic Server 5.1".
You might also like to add the following note to the end of the second
section:
"The above will also work for installing Cocoon in the BEA WebLogic
Enterprise 5.1 J-Engine."
Thanks,
- Phil
-------------------------------------------
Philip Aston - Senior Consultant
BEA Professional Services (Northern Europe)