[
https://issues.apache.org/jira/browse/BEEHIVE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlin Rogers resolved BEEHIVE-1200.
------------------------------------
Resolution: Fixed
Assignee: Julie Zhuo (was: Carlin Rogers)
This was implemented in SVN 550619. The changes include the new optional
<ignore-verify> boolean element for a <url-template> to indicate that the
template factory does not need to verify the required tokens when reading the
template from the beehive-url-template-config.xml. The default NetUI template
factory, DefaultURLTemplatesFactory, was updated to check for the ignore-verify
flag and skip the call to verify() the template if it is set to true.
The changes also include a new test (IgnoreVerify) in the urlTemplates web app.
Also updated the GetURLTemplates test as another template was added to the set
in the config file.
> Update the url-template-config.xsd with an optional element that indicates
> the application does not need to verify a given <url-template>
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1200
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1200
> Project: Beehive
> Issue Type: Improvement
> Components: NetUI
> Affects Versions: 1.0, 1.0.1, 1.0.2
> Reporter: Carlin Rogers
> Assignee: Julie Zhuo
> Fix For: V.Next
>
>
> There's a scenario for an application that uses snippets of URL templates
> that do not have all the default required tokens. The default required tokens
> are defined in the TemplatedURLFormatter class for the template support in
> NetUI URL rewriting. A developer can provide an extension to
> TemplatedURLFormatter and override the set of required tokens for all
> templates in the web app. However, the desired enhancement would be to have
> an optional flag on a template by template basis in
> beehive-url-template-config.xml and be able to basically say it doesn't need
> to verify that the template contains required tokens.
> This enhancement implies modifying the url-template-config.xsd by adding a
> new optional element in the <url-template>, but does not invalidate
> previously valid documents.
> Here's a brief thread in the beehive dev list about the schema change...
> http://mail-archives.apache.org/mod_mbox/beehive-dev/200705.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
