[
https://issues.apache.org/jira/browse/AXIS2-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Loureiro updated AXIS2-4217:
--------------------------------------
Description:
We have several web services deployed on axis2 1.3 war running on Jboss.
We tried to update to axis2-1.4.1 but then our web services clients didn't
function anymore because binding name changed, p. ex:
axis2-1.3:
... <web service namespace>SOAP11Binding ...
and on axis2-1.4.1:
... <web service namespace>Soap11Binding ...
Are we missing something that can avoid this beahviour?
(We deploy ou web services using netbeans plugin, with "automatic" wsdl
generation)
was:
We have several web services deployed on axis2 1.3 war running on Jboss.
We tried to update to axis2-1.4.1 but then our web services clients didn't
function anymore because binding name changed, p. ex:
axis2-1.3:
<web service namespace>SOAP11Binding
and on axis2-1.4.1:
<web service namespace>Soap11Binding
Are you missing something to avoid this beahviour?
We deploy ou web services using netbeans plugin, with "automatic" wsdl
generation
> Unable to use previous web services clients because of changed binding ports'
> name case
> ---------------------------------------------------------------------------------------
>
> Key: AXIS2-4217
> URL: https://issues.apache.org/jira/browse/AXIS2-4217
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.4.1
> Environment: IDE: Netbeans 6.5 with Axis2 plugin 1.2
> Runtime: axis2-1.4.1 running on Jboss 4.0.5
> Reporter: Francisco Loureiro
>
> We have several web services deployed on axis2 1.3 war running on Jboss.
> We tried to update to axis2-1.4.1 but then our web services clients didn't
> function anymore because binding name changed, p. ex:
> axis2-1.3:
> ... <web service namespace>SOAP11Binding ...
> and on axis2-1.4.1:
> ... <web service namespace>Soap11Binding ...
> Are we missing something that can avoid this beahviour?
> (We deploy ou web services using netbeans plugin, with "automatic" wsdl
> generation)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
