[opencms-dev] Legacy content support with OpenCMS as ROOT webappin 6.2

[Jonathan Woods]

And if the no-jk option doesn't work for you (it didn't for me, but maybe
that's because I'm using Apache 1.3.x) then you can always use the more
natural JKUnmount directive, which prevents requests with matching paths
from going through to Tomcat.

Jon 

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Jack Bakker
Sent: 10 March 2006 20:57
To: 'The OpenCms mailing list'
Subject: RE: [opencms-dev] Legacy content support with OpenCMS as ROOT
webappin 6.2


I find the mod_jk / mod_rewrite way of connecting Apache and Tomcat for
OpenCms 6 to offer a lot of control including that which you are looking for
here. There's a tutorial on this approach at www.opencms-forum.de 

I say this because with mod_jk there is the 'no-jk' option which would allow
you to point certain paths to non-Tomcat resources.

..............................
Jack 


________________________________________
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of King, Dennis
Sent: March 10, 2006 3:14 PM
To: opencms-dev at opencms.org
Subject: [Norton AntiSpam] [opencms-dev] Legacy content support with OpenCMS
as ROOT webapp in 6.2

Hi All,
 
I'm busy running through an evaluation of OpenCMS, and am liking what I'm
seeing. However, I have to continue to support /cgi-bin functionality, and
some legacy content outside of OpenCMS, at least for a while. I followed the
Apache/Tomcat integration instructions in the 6.0 documentation to remove
/opencms/opencms from the URLs and it worked fine, even with Tomcat 5.5
instead of 4.x (wasn't sure the CoyoteConnector would be there). However,
though I can access my /cgi-bin directory without trouble because of this
entry (I think):
 
ProxyPass   /cgi-bin/   !
 
I also have this entry:
 
ProxyPass    /support/    !
 
but I am not able to access my $APACHE_DOC_ROOT/support directory unless I
add a symlink to it from $TOMCAT_HOME/webapps/ROOT. I'd prefer not to have
to set up a bunch of symlinks to each directory I want to maintain legacy
content in. Is there a step I've missed or something I can do to achieve
this? It looks like someone else had a similar problem previously; I think
I've paid attention to the info at
 
http://mail.opencms.org/pipermail/opencms-dev/2005q1/015845.html
OpenCMS so far seems to rock! I'm hoping to continue to be impressed.
Thanks!
 
Dennis
 
Apache 2.0.52
Tomcat 5.5
Java 1.4.2
 
My httpd.conf settings:
 
<VirtualHost *:80>
    <Directory "/usr/local/tomcat/webapps/ROOT/">
        Order allow,deny
        Allow from all
    </Directory>
    ServerName www.mysite.com
    ServerAdmin admin at mysite.com
    DocumentRoot "/usr/local/tomcat/webapps/ROOT/"
    ErrorLog logs/error.log
   
    # Log only non-redirect requests in "normal" log file
    SetEnvIf Request_URI "\/opencms\/*" redirect
    CustomLog logs/localhost-access.log common env=!redirect
 
    ProxyPass         /cgi-bin/                 !
    ProxyPass         /support/                 !
    ProxyPass         /opencms/                 !
    RedirectPermanent /opencms/                 http://www.mysite.com
 
    ProxyPass         /resources/               !
    ProxyPass         /export/                  !
   
    ProxyPass         / http://localhost:8081/opencms/
    ProxyPassReverse  / http://localhost:8081/opencms/ </VirtualHost>



_______________________________________________
This mail is sent to you from the opencms-dev mailing list To change your
list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev