[
https://issues.apache.org/jira/browse/VELOCITY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575655#action_12575655
]
Claude Brisson commented on VELOCITY-588:
-----------------------------------------
That is a brillant idea.
As I understand your use cases, the first uberspector in the chain would check
for annotations and, for instance, add log or security.
We are interested, of course. Plus, using chained uberspectors can help us to
factorize existing code.
and I already think to another use case :
a view tool chained uberspector that allows syntaxes like #set( $session.foo =
bar ) instead of #set( $junk = $session.setAttribute('foo','bar')
I may have the time to code that these days, I'm not sure. Let us now if you
start coding it, I'll also add a comment here if I do so first on my side.
> Provide a an ubespector that allows chaining other uberspectors
> ---------------------------------------------------------------
>
> Key: VELOCITY-588
> URL: https://issues.apache.org/jira/browse/VELOCITY-588
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.5
> Reporter: Vincent Massol
> Priority: Minor
>
> In XWiki project we're using Velocity and have a need to write several
> uberspectors that we'd like to chain (see
> http://jira.xwiki.org/jira/browse/XWIKI-2182). We're writing a custom
> uberspector that'll allow chaining other uberspectors but we think that
> uberspector should best be located in the Velocity project if you're
> interested.
> Let us know what you think and if you agree we can donate it to you or you
> could create one from scratch if you agree with the use case.
> Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
