Parameter vales as OMElements
-----------------------------
Key: AXIS2-178
URL: http://issues.apache.org/jira/browse/AXIS2-178
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: deployment
Reporter: Ruchith Udayanga Fernando
An extract from : http://marc.theaimsgroup.com/?l=axis-dev&m=112498008905490&w=2
It'll be much more flexible for the module/service developers if
they can access the XML element describing the parameter as an
OMElement.
This mechanism will enable the developer to store much more than just
a String value in the parameter definition:
<parameter name="mod1:policy" locked="false"
xmlns:mod1="http://my.module.org">
<assersion id="foo"></assersion>
<assersion id="bar"></assersion>
<assersion id="foo_bar"></assersion>
</parameter>
Also consider the following example:
<parameter name="Action" flow="in" locked="xsd:false">UsernameToken</parameter>
<parameter name="Action" flow="out" locked="xsd:false">UsernameToken</parameter>
this will allow setting additional parameter ATTRIBUTES that can be
used to specify the flow. [1]
Ref:
[1] http://marc.theaimsgroup.com/?l=axis-dev&m=112497401724093&w=2
--
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