[
https://issues.apache.org/jira/browse/CXF-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659534#action_12659534
]
Nicola Waters commented on CXF-1954:
------------------------------------
Thank you- turned it was actually re-use of the aegis binding that was causing
the problem. I have now put scope='prototype' on 'aegisBean' and
'string2string' has moved into the correct namespace, namely that of the
service it's being used by.
Other than that everything else configured the same, one
'jaxws-and-aegis-service-factory' bean ref'd by the services. It already had
scope='prototype' on it, so I assume it was behaving properly all along when
ref'd by each service, but the aegis wasn't.
spring-resources_fixed.txt attached to illustrate the difference
I notice that http://cwiki.apache.org/CXF20DOC/http-binding.html points out
that JaxWsServiceFactoryBean isn't re-useable... might be worth adding a
similar note to http://cwiki.apache.org/CXF20DOC/aegis-21.html?
thanks!
> 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
> Attachments: IHolderService.txt, ITemplateService.txt,
> spring-resources.txt, spring-resources_fixed.txt, template_wsdl.txt
>
>
> 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.
