You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jason Pell (JIRA)" <ji...@apache.org> on 2014/12/04 19:01:12 UTC
[jira] [Updated] (CXF-6136) Enhance CXF 2.x JMS Configuration to
better control what exceptions cause rollback
[ https://issues.apache.org/jira/browse/CXF-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-6136:
----------------------------
Summary: Enhance CXF 2.x JMS Configuration to better control what exceptions cause rollback (was: Enhance JMS 2.x JMS Configuration to better control what exceptions cause rollback)
> Enhance CXF 2.x JMS Configuration to better control what exceptions cause rollback
> -----------------------------------------------------------------------------------
>
> Key: CXF-6136
> URL: https://issues.apache.org/jira/browse/CXF-6136
> Project: CXF
> Issue Type: Improvement
> Components: JMS
> Affects Versions: 2.7.14
> Reporter: Jason Pell
> Assignee: Jason Pell
> Priority: Minor
> Fix For: 2.7.15
>
>
> Currently if a JMS Transaction Manager is configured for JMS Configuration style any exceptions thrown by a JAX-WS Implementation will cause a roll back of the message.
> There is no way to distinquish between checked exceptions and runtime exceptions. It would be ideal to be able to have jms services return a normal soap fault message in a reply for checked exceptions defined on the interface, and for runtime exceptions to rollback the message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)