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 "Detelin Yordanov (JIRA)" <ji...@apache.org> on 2014/09/02 22:05:22 UTC
[jira] [Updated] (AXIS2-5668) ServiceBuilder clears any operation's
input wsaw:Action from WSDL
[ https://issues.apache.org/jira/browse/AXIS2-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Detelin Yordanov updated AXIS2-5668:
------------------------------------
Description:
When deploying a service archive that contains a WSDL, any wsaw:Action attributes for operations' input elements get cleared. For example, the following port type operation's input element in WSDL:
{code}
<wsdl:input message="ns:getVersionRequest" wsaw:Action="http://axisversion.sample/VersionPortType/getVersionRequest"/>
{code}
gets converted to one lacking wsaw:Action after deployment:
{code}
<wsdl:input message="ns:getVersionRequest"/>
{code}
The wsaw:Action attributes for operation's output and fault are correctly preserved.
It seems that Axis2 ServiceBuilder first processes the WSDL and populates AxisOperation's {{wsamappingList}}, however when it processes the services.xml file, this list is cleared (assuming there are no action mappings in services.xml).
I guess the {{DescriptionBuilder.processActionMappings}} should be modified not to reset the {{wsamappingList}} if it is non-empty.
was:
When deploying a service archive that contains a WSDL, any wsaw:Action attributes for operations' input elements get cleared. For example, the following port type operation's input element in WSDL:
{code}
<wsdl:input message="ns:getVersionRequest" wsaw:Action="http://axisversion.sample/VersionPortType/getVersionRequest"/>
{code}
gets converted to one lacking wsaw:Action after deployment:
{code}
<wsdl:input message="ns:getVersionRequest"/>
{code}
The wsaw:Action attributes for operation's output and fault are correctly preserved.
It seems that Axis2 ServiceBuilder first processes the WSDL and populates AxisOperation's {{wsamappingList}}, however when it processes the {{services.xml}}, this list is cleared (assuming there are no action mappings in services.xml).
I guess the {{DescriptionBuilder.processActionMappings}} should be modified not to reset the {{wsamappingList}} if it is non-empty.
> ServiceBuilder clears any operation's input wsaw:Action from WSDL
> -----------------------------------------------------------------
>
> Key: AXIS2-5668
> URL: https://issues.apache.org/jira/browse/AXIS2-5668
> Project: Axis2
> Issue Type: Bug
> Components: deployment, kernel
> Affects Versions: 1.6.2
> Reporter: Detelin Yordanov
>
> When deploying a service archive that contains a WSDL, any wsaw:Action attributes for operations' input elements get cleared. For example, the following port type operation's input element in WSDL:
> {code}
> <wsdl:input message="ns:getVersionRequest" wsaw:Action="http://axisversion.sample/VersionPortType/getVersionRequest"/>
> {code}
> gets converted to one lacking wsaw:Action after deployment:
> {code}
> <wsdl:input message="ns:getVersionRequest"/>
> {code}
> The wsaw:Action attributes for operation's output and fault are correctly preserved.
> It seems that Axis2 ServiceBuilder first processes the WSDL and populates AxisOperation's {{wsamappingList}}, however when it processes the services.xml file, this list is cleared (assuming there are no action mappings in services.xml).
> I guess the {{DescriptionBuilder.processActionMappings}} should be modified not to reset the {{wsamappingList}} if it is non-empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org