axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2-178) Parameter values as OMElements
Date Fri, 26 Aug 2005 14:02:27 GMT
     [ ]
Deepal Jayasinghe resolved AXIS2-178:

    Resolution: Fixed

The paramter logic handling will be look like follows
 1. Paramater can be on of the following nature
     <parameter name="hotdeployment" locked="xsd:false">true</parameter>
     <parameter name="hotdeployment" locked="xsd:false">
     < foo>

And if the paramter value is just a text then the prameter type will be TEXT_PARAMETER else
it will be DOM_PARAMETER.

so if it is a text paramter some one can get the parameter vaue as follows

paramrer.getValue() and this will be string value

else it could be OMElment so user of the parameter has to aware of that. and the omelemnt
will be whole paramter element ( <parameter name="hotdeployment" locked="xsd:false">
     < foo>



in addition to that if you know that the paramter is OMElement he/she can acess taht via

paramter.getParameterElement() ; OMElement

> Parameter values as OMElements
> ------------------------------
>          Key: AXIS2-178
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: deployment
>     Reporter: Ruchith Udayanga Fernando

> An extract from :
> 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:
>                        <assersion id="foo"></assersion>
>                        <assersion id="bar"></assersion>
>                        <assersion id="foo_bar"></assersion>
>                </parameter>
> Also consider the following example:
> UsernameToken</parameter>
> UsernameToken</parameter>
> this will allow setting additional parameter ATTRIBUTES that can be
> used to specify the flow. [1]
> Ref: 
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message