Mark Nickel wrote:
> To Ed Knutson,
>
> Ed,
>
> In the FAQ-O-Matic you mention setting up a separate servlet zone for
> Cocoon and a different zone for Jetspeed. I am attempting to implement
> this and am having problems. I am using Cocoon 1.7.0 separate from
> Jetspeed...
Ok, if any of you out there are looking for a way to have xml files
associated with both Jetspeed and Cocoon, here's a way that might work.
As has been mentioned before, under JServ you associate file extentions
like this:
Action cocoon /<my_cocoon_servlet_zone>/org.apache.cocoon.Cocoon
AddHandler cocoon xml
However, this is a global Action. That is, all files, including
defaultPortlets.xml, will be processed by Cocoon.
If you want to make life easy, just do as Ed Knutson advised, make the
Handler for xml files go to Cocoon and rename the Jetspeed xml files to
something like .jxml. Modify your defaultPortles.xml and bamf! Complete
cohabitation!
If you are more adventurous and really really need to have .xml -> Cocoon
*and* .xml -> Jetspeed, then one way under Apache JServ and Apache is to
use Virtual Hosts.
Using Virtual Hosts you will be able to define two different jserv.conf
files. One for a virtual host, A, that associates .xml -> Cocoon and one
for a virtual host, B, that will do .xml -> Jetspeed. (Actually, B won't
have a Handler for .xml files to Cocoon)
Now I haven't actually attempted this because I tried the simple solution.
And that is working just fine. Ok, I'm a bit lazy! :-) I admit it...
Anyway, just wanted to throw that one out there and, for me anyway, put the
Jetspeed - Cocoon cohabitation to rest. At least until I start
experimenting with Jetspeed -> Cocoon -> XSP.
Fun stuff!
Mark
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
