[
https://issues.apache.org/jira/browse/VELOCITY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624303#action_12624303
]
claude edited comment on VELOCITY-588 at 8/21/08 3:00 AM:
------------------------------------------------------------------
I take a quick look to see if what you submitted is sufficient.
At first look, you do implement both "chaining" (where each new uberspector
wraps the previous one) and "linking" (where the first uberspector that returns
non-null is retained).
I'll implement only chaining, since:
- who can do the most can do the least: chaining can simulate linking
- your LinkingUberspector is standalone and will continue to work
was (Author: claude):
I take a quick look to see if what you submitted is sufficient.
> 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
> Fix For: 1.6
>
> Attachments: ChainableUberspectorsXWiki.patch
>
>
> 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]
