You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Liu, Jervis" <jl...@iona.com> on 2006/06/16 08:36:17 UTC

[Patch] patch for WSDL misloading, JIRA 454

Hi, 

Attached please find a patch for WSDL misloading bug, jira http://issues.apache.org/jira/browse/TUSCANY-454 

Basically what happens is that we use "service name + port name" as a unique key to retrieve WSDL definition from WSDL definition cache (See SCDLAssemblyModelLoaderImpl.java and WebServiceBindingImpl.java). When web service applications are hosted in a standalone web service container or any J2EE container, normally we can use WSDL file location URL to uniquely identify a web service in container, though it is also valid to use the combination of service name and port name as a unique key. The latter is the way how Tuscany uniquely identifies a web service app hosted in Tomcat. However in the case of Tuscany SCA demos, several demos that are deployed in Tomcat are using exact same wsdl files  <<helloworlde4xws.patch>>  <<helloworldjsclient.patch>> (helloworldws, helloworlde4xws and helloworldjsclient), thus same service name + port name. This caused wrong wsdl defintion was retrieved from cache. 

I fixed this issue by changing those offending demos to have their own service name and port name in WSDL.  

Can someone kindly review and apply please. BTW, I am sorry that I have to provide two separate patches. For some unknown reasons, I always get an error message if I try to create a patch from samples directory. Thanks.

Cheers,
Jervis