You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/12/11 10:50:09 UTC
[jira] Updated: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Gavlin updated SM-1726:
---------------------------
Description:
The CXF JMS transport was recently re-written to be based on Spring JMS. Assuming that issue http://issues.apache.org/jira/browse/CXF-180 is now resolved, it should be possible for the smx-cxf-bc consumer to be configured with a transactional JMS transport. In this situation, the smx-cxf-bc consumer must recognize that the CXF JMS transport is transaction-enabled and send a transactional exchange to the NMR accordingly.
A test case should be written to demonstrate this functionality and ensure that it is working as designed.
It would be useful to demonstrate this with both:
1. a wsdl-based configuration <jms:server transactional="true"/>
2. a cxfbc:features-based configuration (see SM-1725)
was:
The CXF JMS transport was recently re-written to be based on Spring JMS. Assuming that issue http://issues.apache.org/jira/browse/CXF-180 is now resolved, it should be possible for the smx-cxf-bc consumer to be configured with a transactional JMS transport. In this situation, the smx-cxf-bc consumer must recognize that the CXF JMS transport is transaction-enabled and send a transactional exchange to the NMR accordingly.
A test case should be written to demonstrate this functionality and ensure that it is working as designed.
> Develop test case to demonstrate and verify that smx-cxf-bc consumer endpoint with transactional JMS transport sends transactional exchange correctly
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1726
> URL: https://issues.apache.org/activemq/browse/SM-1726
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-cxf-bc
> Affects Versions: servicemix-cxf-bc-2008.01
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
>
> The CXF JMS transport was recently re-written to be based on Spring JMS. Assuming that issue http://issues.apache.org/jira/browse/CXF-180 is now resolved, it should be possible for the smx-cxf-bc consumer to be configured with a transactional JMS transport. In this situation, the smx-cxf-bc consumer must recognize that the CXF JMS transport is transaction-enabled and send a transactional exchange to the NMR accordingly.
> A test case should be written to demonstrate this functionality and ensure that it is working as designed.
> It would be useful to demonstrate this with both:
> 1. a wsdl-based configuration <jms:server transactional="true"/>
> 2. a cxfbc:features-based configuration (see SM-1725)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.