[
https://issues.apache.org/activemq/browse/SMXCOMP-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54987#action_54987
]
Richard Sladek commented on SMXCOMP-13:
---------------------------------------
Hello,
I've tried the new code from trunk but it is still not working as expected -
both faultcode and faultstring are not propagated from the original soap fault
message.
Empty SOAP Fault message is always returned instead:
<faultcode>soapenv:Server</faultcode>
<faultstring></faultstring>
After some investigation I modified the code as follows:
fault.setProperty(JBIMarshaler.SOAP_FAULT_CODE,
soapFault.getCode());
fault.setProperty(JBIMarshaler.SOAP_FAULT_REASON,
soapFault.getReason());
fault.setProperty(JBIMarshaler.SOAP_FAULT_NODE,
soapFault.getNode());
fault.setProperty(JBIMarshaler.SOAP_FAULT_ROLE,
soapFault.getRole());
and now it works like a charm!
Obviously, calling just fault.setContent(soapFault.getDetails()); is not enough.
> smx-jms MultiplexingProviderProcessor onMessage() does not send error
> exchanges for Exceptions nor does it set exchange Faults correctly
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-13
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-13
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-jms
> Affects Versions: 3.2.3
> Reporter: Ron Gavlin
> Priority: Critical
> Fix For: servicemix-jms-2009.02
>
> Attachments: sm-1678.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
