[
https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386662#comment-14386662
]
Jochen Riedlinger commented on CXF-6274:
----------------------------------------
no, that's not the thing you should/can improve! The NullPOinterException just
points out that something went terribly wrong before....
What you should improve is that the RMCaptureInInterceptor always has to be
activated together with all other WS-RM interceptors. At least it has to be
activated when the persistent store is present an not only the unreliable
"in-memory persistence".
This is definitive a bug. (Or you write in the documentation that using WS-RM
is only possible when doing the interceptor-chain configuration completety
manually and not by just configuring "<wsrm-mgr:rmManager ......."
At this point http://cxf.apache.org/docs/wsrmconfiguration.html is
incomplete/wrong)
> 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)
