You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Oliver Jelinski (JIRA)" <ji...@apache.org> on 2011/09/23 14:34:26 UTC
[jira] [Closed] (CAMEL-4254) Missing setter or constructor-argument
for elementNameStrategyRef in SoapJaxbDataFormat
[ https://issues.apache.org/jira/browse/CAMEL-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Jelinski closed CAMEL-4254.
----------------------------------
It works. Thanx.
> Missing setter or constructor-argument for elementNameStrategyRef in SoapJaxbDataFormat
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-4254
> URL: https://issues.apache.org/jira/browse/CAMEL-4254
> Project: Camel
> Issue Type: Bug
> Components: camel-soap
> Affects Versions: 2.7.0, 2.7.3
> Reporter: Oliver Jelinski
> Assignee: Willem Jiang
> Fix For: 2.8.1, 2.9.0
>
> Attachments: camel-soap-2.7.3.patch.txt
>
>
> Because the variable "elementNameStrategyRef" in org.apache.camel.dataformat.soap.SoapJaxbDataFormat can't be set, it is always null. Therefore declaring the data format with spring-dsl leads to an automatic fallback to the default strategy "TypeNameStrategy" in org.apache.camel.dataformat.soap.SoapJaxbDataFormat.checkElementNameStrategy(Exchange exchange). This further leads to wrong results when marshalling.
> So the following declararion does not work correctly:
> ...
> <bean id="myStrategy" class="org.apache.camel.dataformat.soap.name.ServiceInterfaceStrategy">
> <constructor-arg value="my.package.MyServiceInterface"/>
> <constructor-arg value="true"/>
> </bean>
> ...
> <camelContext xmlns="http://camel.apache.org/schema/spring">
> ...
> <dataFormats>
> <soapjaxb id="mySoap"
> contextPath="my.package"
> elementNameStrategyRef="myStrategy"/>
> </dataFormats>
> ...
> <route>
> <from uri="cxf:/MyService?serviceClass=my.package.MyServiceInterface" />
> ...
> <convertBodyTo type="my.package.MyType"/>
> <marshal ref="mySoap"/>
> ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira