Hello,
I'm trying to setup a "custom" component root and a "common" component
root in mason so that the custom adds and replaces a small subset of
files in the common one for changes to behavior and look-and-feel across
similar systems.
I'm running into a problem with this while using DirectoryIndex and
would like any suggestions to make the DirectoryIndex behavior work
across the "merged" component roots. Eventually, I was thinking of
using quite a few more than two component roots...
======
In httpd.conf I have:
DocumentRoot /code/mason.custom
<Directory /code/mason.custom>
DirectoryIndex index.html
SetHandler perl-script
PerlHandler HTML::Mason::ApacheHandler
PerlAddVar MasonCompRoot "custom => /code/mason.custom"
PerlAddVar MasonCompRoot "common => /code/mason.common"
PerlSetVar MasonDataDir /code/masondata
Allow from all
</Directory>
======
On disk I have:
/code/mason.common/index.html
/code/mason.common/directory
/code/mason.common/directory/index.html
/code/mason.custom/index.html
/code/mason.custom/added.html
======
I get a 404 for URL http://localhost/directory/
I get a 200 for URL http://localhost/directory/index.html
Ideally, http://localhost/directory/ would realize that index.html
exists in /code/mason.common and thus can be handled by Mason.
Do I need to roll my own wrapper around Mason, use a dhandler, change my
httpd.conf, ...?
Thanks in advance,
Matthew
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
