cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Pell <>
Subject Re: JMS SessionTransacted
Date Thu, 04 Dec 2014 15:52:33 GMT
Yep it does work with the JMSTransactionManager set.  So I guess its just a
documentation issue then.

If I want some exceptions to be handled as soap faults - in a reply
message, and some exceptions to cause rollback.

Is that possible in cxf once i have enabled the JMSTransactionManager?

I note the JMSDestination wraps non runtime exceptions in runtime
exceptions., but ideally if I throw a business fault (a checked exception),
then I would do the normal fault processing and send a response message
with the fault.

Any runtime exceptions would cause a roll back.

Is there some cxf interceptor magic I might be able to do?

On Fri, Dec 5, 2014 at 2:09 AM, Christian Schneider <
> wrote:

> Yes. For CXF 2.x you need a spring PlatformTransactionManager. This can
> then be a specific manager for JMS or a real JTA Transaction manager.
> Does it then work?
> Christian
> On 04.12.2014 15:34, Jason Pell wrote:
>> I have set this to true in the JMSCOnfiguration
>> I am using CXF 2.7.x.  I cannot upgrade to 3.x, so I need to get this
>> working using the JMS Configuration style.
>> What I am trying to get working is JMS managed transactions.  So If I
>> throw
>> an runtime exception from my JAX-WS Implementation, I would expect the
>> message to be rolled back.
>> However this does not work as expected.  The JMSDestination expects a
>> PlatformTransactionManager to be configured in order for the rollback
>> process of the JMS Listener in spring to be executed.
>> I managed to get further by using
>> jmsConfig.setTransactionManager(new
>> JmsTransactionManager(connectionFactory));
>> Is this a bug in the cxf jms support or am I misunderstanding?
> --
> Christian Schneider
> Open Source Architect

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message