You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2005/08/25 16:48:08 UTC
[jira] Created: (AXIS2-178) Parameter vales as OMElements
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
Re: [jira] Commented: (AXIS2-178) Parameter values as OMElements
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chinthka
see my comments below;
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Eran Chinthaka (JIRA)" <ji...@apache.org>
To: <ax...@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
>
>
[jira] Commented: (AXIS2-178) Parameter values as OMElements
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (AXIS2-178) Parameter values as OMElements
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-178?page=all ]
Ruchith Udayanga Fernando updated AXIS2-178:
--------------------------------------------
Summary: Parameter values as OMElements (was: Parameter vales as OMElements)
Description:
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
was:
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
corrected a typo in the title :-)
> 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
[jira] Resolved: (AXIS2-178) Parameter values as OMElements
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-178?page=all ]
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>
.......................
</foo>
</parameter>
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>
.......................
</foo>
</parameter>
)
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: 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
[jira] Commented: (AXIS2-178) Parameter values as OMElements
Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-178?page=comments#action_12320147 ]
Ajith Harshana Ranabahu commented on AXIS2-178:
-----------------------------------------------
why do we need to have two methods ? hmmm.. make the common case easy!
> 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