[ http://issues.apache.org/jira/browse/AXIS2-178?page=comments#action_12320145 ]
Eran Chinthaka commented on AXIS2-178: -------------------------------------- Deepal, Just some thoughts. why do we need to have two methods ? Can we have just one method, getParameterElement(). If user know that its just text, he can : getParameterElement().getText() will do. And if the parameter type is TEXT and if the parameter has an attribute, then user can't access it using the getValue. So I'd like to have just one method. Plus, I think the type of the parameter should ELEMENT_PARAMETER or OM_PARAMETER., not *DOM*_PARAMETER. > Parameter values 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: > > <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] 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
