[
https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386675#comment-14386675
]
Jochen Riedlinger commented on CXF-6274:
----------------------------------------
Hi Aki,
no that's the point. By using the WSRM feature or the WSRM policy to configure
WSRM the mentioned interceptor is not in the chain. I think the
"auto-configuration" part misses to put the capture interceptor in the chain
and so the data is not there in the later execution. I have to put in the chain
(and don't like to do that) to make it work.
Best regards,
Jochen
P.S.: Meanwhile we found out that WSRM is not reliable at all in the current
implementation (tested with 3.0.4 and 2.7.14). See CXF-6323
> NullPointerException in DestinationSequence because of RMCaptureInInterceptor
> not in interceptor chain
> ------------------------------------------------------------------------------------------------------
>
> Key: CXF-6274
> URL: https://issues.apache.org/jira/browse/CXF-6274
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.0.4
> Reporter: Jochen Riedlinger
> Assignee: Akitoshi Yoshida
> Labels: WS-RM, WS-ReliableMessaging
> Fix For: 3.0.5
>
> Attachments: cxf-servlet.xml, ws-rm_saml.wsdl
>
>
> I'm building a prototype webservice using one-way WS-RM (in combination with
> SAML sender vouches).
> It works well as long as there's no persistence store configured.
> When using a jdbcStore (Oracle DB) I get this NullPointerException:
> 11:19:27,214 WARNING [org.apache.cxf.phase.PhaseInterceptorChain]
> (http-/0.0.0.0:8080-1) Interceptor for
> {...}CMLResponseManagerAsyncWSService#{...}respondGetInfo has thrown
> exception, unwinding now: java.lang.NullPointerException
> at
> org.apache.cxf.ws.rm.DestinationSequence.acknowledge(DestinationSequence.java:171)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)