axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe" <dee...@opensource.lk>
Subject Re: [jira] Commented: (AXIS2-178) Parameter values as OMElements
Date Fri, 26 Aug 2005 14:35:19 GMT
Hi Chinthka

see my comments below;

Thanks,
 Deepal
................................................................
~Future is Open~



----- Original Message ----- 
From: "Eran Chinthaka (JIRA)" <jira@apache.org>
To: <axis-dev@ws.apache.org>
Sent: Friday, August 26, 2005 8:24 PM
Subject: [jira] Commented: (AXIS2-178) Parameter values as OMElements


>    [ 
> 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.

Yes it will , but I tried to make the simple case easier , almost wll the 
time value of the paramter will be just a text so if that is the case user 
can get the parameter value by   (String)paramter.getValue();


> 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.

we are not allowd to have more attribute in current implementation only the 
"name" and "locked" valid.

>
> Plus, I think  the type of the parameter should ELEMENT_PARAMETER or 
> OM_PARAMETER., not
*DOM*_PARAMETER.

+1 , I just used a constant in the Paramter , happy to change that

>
>> 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
>
> 



Mime
View raw message