Ok, here's some pushback...
i'm not sure i like putting the path restrictions down as a scope.
a) it causes the value into ServletToolInfo.setScope() to not match getScope()
b) what if you want to restrict a session/application oriented tool to certain paths?
what do you think about making the path a totally separate property of ServletToolInfo? i know that makes things more complicated, especially in ServletToolboxManager.getToolbox() if we want to path-restrict session/application tools. Maybe to start things off we could have the path restriction as a separate property and add a fourth "request-path" scope option. Then we don't get a set/getScope mismatch and still limit path restriction to request scope (simplifying getToolbox()) but leave open the possibility of allowing session or application tools to be path-restricted.
thoughts anyone (esp Claude)?