remove schema constraints on key element in url-templates-config.xsd
--------------------------------------------------------------------
Key: BEEHIVE-840
URL: http://issues.apache.org/jira/browse/BEEHIVE-840
Project: Beehive
Type: Bug
Components: NetUI
Versions: v1m1
Reporter: Carlin Rogers
Assigned to: Carlin Rogers
Priority: Minor
Fix For: V1
To keep the URL template framework for a broader range of use cases, it would
be useful not to have the
restriction requiring key to be one of "action", "secure-action", "resource",
"secure-resource", "render",
"secure-render".
I'd like to remove these constraints on the element "key" in this schema.
There's a use case where the
URLs may not be used in JSPs, but in a WSDL. The key names "action", "render"
do not make sense
in this context. For example, in a WSDL use case, the key values are based on
the WSDL port names.
So the Key element will just be a string. This make the url template schema a
little more general.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
