You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2009/11/03 13:31:52 UTC
[jira] Created: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Rollback does not work for transactional routes using camel-cxf
---------------------------------------------------------------
Key: CAMEL-2128
URL: https://issues.apache.org/activemq/browse/CAMEL-2128
Project: Apache Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.0.0
Reporter: Christian Schneider
I have a request reply service that should be able to do three different
things:
1) no exception occurs in the implementation: The jms Message should be
committed and the normal reply should be sent
2) The implementation throws an exception defined in the service contract:
The jms message should be committed and a fault should be sent
3) The implemementation throws another kind of exception: The message delivery should
be rolled back so it can be received again
Case 1 and 2 currently work as expected.
For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider closed CAMEL-2128.
--------------------------------------
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55193#action_55193 ]
Willem Jiang commented on CAMEL-2128:
-------------------------------------
@Christian,
I just found this fix broken the old camel transport example , which don't want to camel error handle to be involved.
I will create a new JIRA to add a flag on the CamelTransportFactory to enable this feature.
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CAMEL-2128:
---------------------------------------
Attachment: patch.txt
Patch from Willem
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CAMEL-2128:
---------------------------------------
Patch Info: [Patch Available]
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55144#action_55144 ]
Christian Schneider commented on CAMEL-2128:
--------------------------------------------
I have managed to route my special NoSuchCustomerException so that it will commit and return a fault by using the following camel context.
While I still think the defined exceptions should be handled as a Soap Fault by default this at least means that my transactional CXF Service works. So I think the patch from Willem should go into trunk.
<camelContext id="camelContext" trace="false" xmlns="http://camel.apache.org/schema/spring">
<onException>
<exception>net.enbw.services.etg.examples.customerservice.NoSuchCustomerException</exception>
<handled><constant>true</constant></handled>
</onException>
<route>
<from uri="direct:client"/>
<to uri="jms://queue.net.enbw.services.etg.examples.customerservice.CustomerService" />
</route>
<route>
<from uri="jms://queue.net.enbw.services.etg.examples.customerservice.CustomerService" />
<transacted/>
<to uri="direct:server"/>
</route>
</camelContext>
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-2128.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
1.6.2
trunk
http://svn.apache.org/viewvc?rev=832647&view=rev
camel 1.x branch
http://svn.apache.org/viewvc?rev=832648&view=rev
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55142#action_55142 ]
Christian Schneider commented on CAMEL-2128:
--------------------------------------------
I have built a camel-cxf module that includes the patch. Now the rollback
basically works.
The problem is that it happens for all exceptions. I think a good default
would be to return a fault for all exceptions that the service explicitly
defines and roll back for all other exceptions. The problem is I have no
idea how this could be done.
In the meantime I will try to use an onException() clause to do this
differentiation.
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55140#action_55140 ]
Christian Schneider commented on CAMEL-2128:
--------------------------------------------
Willem Jiang has created a patch that partly resolves this issue:
### Eclipse Workspace Patch 1.0
#P camel-cxf
Index:
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
===================================================================
---
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
(revision 831871)
+++
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
(working copy)
@@ -271,6 +271,12 @@
propagateResponseHeadersToCamel(outMessage, camelExchange);
+ // check if the outMessage has an exception
+ Exception exception = outMessage.getContent(Exception.class);
+ if (exception != null) {
+ camelExchange.setException(exception);
+ }
+
CachedOutputStream outputStream =
(CachedOutputStream)outMessage.getContent(OutputStream.class);
camelExchange.getOut().setBody(outputStream.getBytes());
getLogger().log(Level.FINE, "send the response message: "
+ outputStream);
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-2128) Rollback does not work
for transactional routes using camel-cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55193#action_55193 ]
Willem Jiang edited comment on CAMEL-2128 at 11/6/09 3:28 AM:
--------------------------------------------------------------
@Christian,
I just found this fix broken the old camel transport example , which don't want to camel error handle to be involved.
I will create a new JIRA CAMEL-2142 to add a flag on the CamelTransportFactory to enable this feature.
was (Author: njiang):
@Christian,
I just found this fix broken the old camel transport example , which don't want to camel error handle to be involved.
I will create a new JIRA to add a flag on the CamelTransportFactory to enable this feature.
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55139#action_55139 ]
Christian Schneider commented on CAMEL-2128:
--------------------------------------------
Also see the thread Problem with SOAP/JMS and transactions in the user list:
http://mail-archives.apache.org/mod_mbox/camel-users/200911.mbox/thread
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-2128:
-----------------------------------
Assignee: Willem Jiang
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55151#action_55151 ]
Willem Jiang commented on CAMEL-2128:
-------------------------------------
@Christian
It is hard to let CamelTransport to know which kind of exception is defined by User, and the CamelTransport should now nothing about the application level thing. Let's put the ignoring the customer exception on the camel's error handler framework.
I will commit my patch in a min :)
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-2128) Rollback does not work for
transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CAMEL-2128:
---------------------------------------
Attachment: appcontext.xml
Sample Applicationcontext that contains a transactional route that forwards from jms to a cxf service
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-2128) Rollback does not work
for transactional routes using camel-cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55140#action_55140 ]
Christian Schneider edited comment on CAMEL-2128 at 11/3/09 4:36 AM:
---------------------------------------------------------------------
Willem Jiang has created a patch that partly resolves this issue:
was (Author: chris@die-schneider.net):
Willem Jiang has created a patch that partly resolves this issue:
### Eclipse Workspace Patch 1.0
#P camel-cxf
Index:
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
===================================================================
---
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
(revision 831871)
+++
src/main/java/org/apache/camel/component/cxf/transport/CamelDestination.java
(working copy)
@@ -271,6 +271,12 @@
propagateResponseHeadersToCamel(outMessage, camelExchange);
+ // check if the outMessage has an exception
+ Exception exception = outMessage.getContent(Exception.class);
+ if (exception != null) {
+ camelExchange.setException(exception);
+ }
+
CachedOutputStream outputStream =
(CachedOutputStream)outMessage.getContent(OutputStream.class);
camelExchange.getOut().setBody(outputStream.getBytes());
getLogger().log(Level.FINE, "send the response message: "
+ outputStream);
> Rollback does not work for transactional routes using camel-cxf
> ---------------------------------------------------------------
>
> Key: CAMEL-2128
> URL: https://issues.apache.org/activemq/browse/CAMEL-2128
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.0.0
> Reporter: Christian Schneider
> Attachments: appcontext.xml, patch.txt
>
>
> I have a request reply service that should be able to do three different
> things:
> 1) no exception occurs in the implementation: The jms Message should be
> committed and the normal reply should be sent
> 2) The implementation throws an exception defined in the service contract:
> The jms message should be committed and a fault should be sent
> 3) The implemementation throws another kind of exception: The message delivery should
> be rolled back so it can be received again
> Case 1 and 2 currently work as expected.
> For Case 3 a fault is returned to the caller and the transaction is committed which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.