cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Waters (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-1954) string2string - Map Types- into wrong namespace
Date Mon, 22 Dec 2008 14:54:44 GMT
string2string - Map Types-  into wrong namespace
------------------------------------------------

                 Key: CXF-1954
                 URL: https://issues.apache.org/jira/browse/CXF-1954
             Project: CXF
          Issue Type: Bug
          Components: Aegis Databinding
    Affects Versions: 2.1.3
            Reporter: Nicola Waters


CXF 2.1.3, being deployed in Tomcat. Multiple services inside the application, java2wsdl,
configured with Spring.

A service containing a method with one parameter as a java.util.Map, results in a wsdl error-
the Type for the map, namely  'string2string', ends up in the wrong namespace. Instead of
going into the service's namespace, the Type is bound to the namespace of whatever the first
service deployed into the application was.

i.e. if you have say, 2 services deployed, wired in Spring in this order:

com.test.Service1  (namespace:   http://service1.test.com
com.test.Service2 (namespaceL http://service2.test.com)

and Service2 contains
 constructContents(String siteId, String templateName, Map<String, String> contentsMap)
throws TemplateException;

the resulting wsdl for Service2, will have its   
complexType name="string2stringMap"
attached to the namespace 'http://service1.test.com'

Relevant sections of Spring config, java and resulting wsdl attached.

At the moment 'Map' is the only type I've found that causes this problem.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message