11/20/2002 7:35:50 AM, "V. Cekvenich" <[EMAIL PROTECTED]>
wrote:
>The other things with the prefix, is that it maps nicely with CMA
>security for the modules.
>Ex: Only users in the Admin role can go to /admin/*.
>etc.
>
>.V
Actually, prefix mapping works just fine with container-
basedsecurity. You just include the prefix with the constraint:
<web-resource-name>Administrative</web-resource-name>
<!-- The URLs to protect -->
<url-pattern>/do/admin/*</url-pattern>
</web-resource-collection>
It's also possible that this strategy could also be applied to
modules. Instead of declaring your modules to be "payables/", we
might be able to accept "do/payables/" where /do/* is mapped to
the ActionServlet.
The gotcha would be an assumption that there are no slashes in the
module name. But since there is already a flag for prefix
matching, that's something we could watch for.
Another approach might be to use the existing prefix matching flag
to automatically prepend the prefix. We couldn't do that at first
because it would mean the pages would have to be stored under /do/
too, which wouldn't work. But, we've since added a setting to
munge the path used to find the pages (so they can be placed under
/WEBINF/$MODULE for example). We should be able to use that
feature to relocate the pages so that they are not directly under
/do/, and get the system to look under
/pages/do/payable
or
/WEBINF/do/payable
instead.
Unforunately, everything I have open right now is 1.0, and so I
can't run any quick tests.
-Ted.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
