[ http://issues.apache.org/jira/browse/VELTOOLS-62?page=comments#action_12435497 ] Nathan Bubna commented on VELTOOLS-62: --------------------------------------
To overlap with Claude's answer to Henning.. For VelocityTools, scope doesn't really refer to the scope of a tool's visibility. Rather, it refers to the scope of its lifecycle. This enhancement was proposed as a way to restrict and validate the configured scope of a tool. It wasn't suggesting that a tool should determine its own scope. Though, we could potentially extend the concept to allow that as well. I can easily imagine some sort of preferred-scope annotation that would allow users to leave off the scope part of their toolbox configuration. Something to think about for the future... To answer Claude... I'm not sure when VelocityTools will target jdk 1.5. My instinct is to say that we won't until Velocity does. However, i'm sorely tempted to begin targetting it with VelocityTools 2.0 (which is probably a lot closer than Velocity 2.0). We may be able to do that and continue supporting jdk 1.4 in similar fashion to Struts 2.0 (with retroweaver et al). in the meantime, i may still add the check for getValidScopes() to VelocityTools 1.3, since i think it is a good idea and not that much trouble. :) certainly much less trouble than adding xdoclet as a dep for this. > New empty interfaces that allow one to enforce the scope of a tool > ------------------------------------------------------------------ > > Key: VELTOOLS-62 > URL: http://issues.apache.org/jira/browse/VELTOOLS-62 > Project: VelocityTools > Issue Type: Improvement > Reporter: Claude Brisson > Priority: Minor > Attachments: ApplicationTool.java, RequestTool.java, > ServletToolboxManager.patch, SessionTool.java > > > This is a proposal. Once that a tool implements at least one of the three > interfaces RequestTool, SessionTool or ApplicationTool, it means that the > actual scope of the tool must correspond to one of the interfaces the tool is > implementing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
