[
https://issues.apache.org/jira/browse/VELOCITY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-588.
-------------------------------------
Resolution: Fixed
Assignee: Claude Brisson
ok, I implemented uberspectors chaining using Sergiu Dumitriu's work.
Now you can specify several class names in runtime.introspector.uberspect.
For each non-leftmost uberspector:
- if it implements ChainableUberspector then the chaining is made by calling
its wrap method
- if it doesn't, then the chaining is made via the LinkingUberspector utility
class that takes two uberspectors
Added a testcase and updated docs.
> 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
> Assignee: Claude Brisson
> 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]
