Yes, unfortunately the wildcard aspect of request path restrictions is
broken for any wildcard paths longer than the scope of the tool (so
longer than 7 chars for a request-scoped tool). I noticed this
shortly after the release and have fixed it. I'm thinking about
trying to put a 1.3.1 release together, but i was not expecting this
(obviously). So, it may take me a week or so to figure out where in
my schedule to make time for this, and then another week or two to get
the release out. If you can't wait for the fix, then feel free to
check out the latest code from the trunk in Subversion, build it
yourself, and use that.
On 4/2/07, David Donohue <[EMAIL PROTECTED]> wrote:
Hello!
I am finding the request-path in toolbox.xml does not behave as I would
expect when I use the wildcard *
I am using Velocity 1.5, VelocityTools 1.3, and the ClasspathResourceLoader,
with this in velocity.properties:
class.resource.loader.class =
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
In toolbox.xml, I am loading my custom tool fine when I specify a single
path
<tool>
<key>mytool</key>
<scope>request</scope>
<class>my.Tool</class>
<request-path>/my/webdocs/myToolPage.vm</request-path>
</tool>
but when i use a wildcard, my tool is being loaded every single URL (not
just for URLs starting with the specified path)
<tool>
<key>mytool</key>
<scope>request</scope>
<class>my.Tool</class>
<request-path>/my/webdocs/tools/*</request-path>
</tool>
Thanks!
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
