[
https://issues.apache.org/jira/browse/VELOCITY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604030#action_12604030 ]
Nathan Bubna commented on VELOCITY-588:
---------------------------------------
Hi Sergiu,
My apologies for my slow response. But today i'm catching up on some Velocity stuff. :)
This looks pretty good. Should i assume that it is working well for you? I only wonder if it might be simpler to keep Uberspectors in an ordered list (in the root/parent Uberspector) and just interrogate them in order until one returns a non-null value. This way you might be able to avoid requiring them to implement a ChainableUberspector interface.
Of course, i haven't tried implementing it that way. Have you? What do you think of the idea?
> 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
> 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:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
