> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
> Juffer
> Sent: giovedě 12 luglio 2001 15.11
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> Luca Morandini wrote:
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Andre
> > > Juffer
> > > Sent: giovedě 12 luglio 2001 13.35
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: C1 to C2
> > >
> >
> > Hmmm... why you would like to start a different context ?
> > I assumed you wanted just to put you application in a
> directory other than
> > \webapps\cocoon... am I wrong ?
>
>
> You are entirely correct. That is exactly what I have in mind. I should
> say that all static html (normally in public_html in user's
> subdirectories, as is common under Unix) are still served directly by
> the Apache webserver. Nothing of that is going through cocoon. Under
> cocoon1, one uses tomcat where files with the extension .xml where
> served by tomcat and ultimately by cocoon1. I was under the impression
> that things with cocoon2 were done in a similar way, but maybe
> everything should be served by cocoon2 first (including these html
> files) and the sitemap would than start the appropriate pipelines? (That
> would explain the word sitemap). So, cocoon2 would control the complete
> website (both static and dynamic files). Is the Apache webserver in fact
> still required to run on the server?
>
No, you could dispense with Apache and run everything on Tomcat, though it
seems an overkill to me (and less stable, too).
Talking about C2, there is no need to start another Cocoon context, far
from it... you should just tell Cocoon to find your files where they are.
The mechanism to do that is to modify the sitemap (the one I've named
"general sitemap" in my previous message) in order to mount the sub-sitemap
correctly.
The odd thihg about this is that you may find your site only by referring
to an URI with "cocoon" in it, like <...>\cocoon\cru\index.xml.
Next step is to tell Apache to redirect everything from "cru" to
"coocon\cru" (provided, of course, "cru" is the name of you application);
I've used the rewrite engine of Apache, adding the following to httpd.conf:
RewriteEngine On
RewriteLog "C:/apps/apache/logs/rewrite.log"
RewriteLogLevel 0
RewriteRule cru/(.*) /cocoon/cru/$1 [PT]
It works, but it took me half a day to figure it out the whole process :(
Best regards,
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
+39 0744 59 85 1 Office
+39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
