You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/02/26 14:28:00 UTC

[jira] Commented: (SMXCOMP-466) WS-RM : the CreateSequenceResponse body is void

    [ https://issues.apache.org/activemq/browse/SMXCOMP-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50038#action_50038 ] 

Freeman Fang commented on SMXCOMP-466:
--------------------------------------

Hi,
If you can attach testcase to expose this problem, it would be great.
Thanks
Freeman

> WS-RM : the CreateSequenceResponse body is void
> -----------------------------------------------
>
>                 Key: SMXCOMP-466
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-466
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>         Environment: WIndws XP
>            Reporter: Francois Mireaux
>         Attachments: smx-cxfbc.patch
>
>
> When WS-RM is activated, the CreateSequence request is correctly treated and a CreateSequenceResponse body is created and stored in content as List. But the only out interceptor JbiOutWsdl1Interceptor set by CxfBcConsumer is only aware of Source content and the resulted body is void which leads to an client error.
> The proposed path of CxfBcConsumer adds two new out interceptor to the endpoint list WrappedOutInterceptor and BareOutInterceptor. Tests are OK but I am far to be sure that's the good solution or the best one.
> Note : the RM surefire tests seems to test the CXF WS-RM capacities rather than the servicemix-cxf-bc one's.

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