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/10 07:22:06 UTC
[jira] Created: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
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
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SM-1726 started by Freeman Fang.
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48174#action_48174 ]
Willem Jiang commented on SM-1726:
----------------------------------
I just add an transaction example(System unitest org.apache.cxf.systest.jms.tx) for CXF-180, please check latest CXF trunk for it.
> 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.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48259#action_48259 ]
Freeman Fang commented on SM-1726:
----------------------------------
Hi Ron,
You said "recognize that the CXF JMS transport is transaction-enabled and send a transactional exchange to the NMR accordingly", do you mean if we detect the cxf bc consumer over jms transport is transaction-enabled (actually it's cxf over jms server side is transaction-enabled), we should do something in CxfBcConsumer like
TransactionManager tm = (TransactionManager) getContext().getTransactionManager();
tm.begin();
InOut me = createInOut();
getContext().getDeliveryChannel().sendSync(me);
// retrieve the out message
me.setStatus(ExchangeStatus.DONE);
getContext().getDeliveryChannel().send(me);
tm.commit();
This is my first understanding for your description and honestly I agree with it for my first thought.
But after going through the code in servicemix-jms consumer (which is also used as transaction component)and realizing how cxf jms server transaction works, I believe we needn't do things like tm.begin()/tm.commit() in CxfBcConsumer.
Let's say the work flow is
external client <=======> cxf bc consumer over jms with transaction enabled <===========> whatever in the JBI container
The cxf bc consumer(which actually is a kind of cxf server) itself will determine to rollback and redeliver if get some exception, all rollback/commit stuff should be done by cxf jms server it self.
That's also the way how servicemix-jms component do the transaction, what we need is just set the transactionManager and needn't do things like tm.begin()/tm.commit() explicitly.
IMO, what we need do is
1. inject the transactionManager which is used by the jbi container to cxf
JMSDestination.
2. when we found the cxf bc consumer is transaction enabled, we need always
use sendSync() to send out message to the NMR, since as Willem point,
only sync is supported in case of transaction enabled.
3. we also need consider how to filter the expected exception(like some fault defined in the wsdl) to avoid causing rollback.
Currently it specified in TranscationProxyFactoryBean(the wrapper of the implementator) in cxf-180 test, but for smx, the cxf bc consumer may connect anything inside JBI container, which means we have no concept of implementor at all.
What do you think?
Freeman
> 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.
[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
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48328#action_48328 ]
Freeman Fang commented on SM-1726:
----------------------------------
add wsdl-onlyy configuration test
http://svn.apache.org/viewvc?rev=729306&view=rev
> 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.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48327#action_48327 ]
Freeman Fang commented on SM-1726:
----------------------------------
the wsdl-only configuration should work since we reuse transactionMangeer used by jbi container, we only need configure transactionManager across the jbi container level (the configuration for transactionManager already there in the kit).
So for cxf bc consumer add transactional="true" for jms:server in wsdl should be enough
will add testcase for it later on
> 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.
[jira] Assigned: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SM-1726:
--------------------------------
Assignee: Freeman Fang
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48325#action_48325 ]
Freeman Fang commented on SM-1726:
----------------------------------
commit
http://svn.apache.org/viewvc?rev=729254&view=rev to 3.2 branch
Note: currently the configuration for enabling transcation is by jms features config in spring, still figuring out how to make wsdl-only configuration work even it's not supported in cxf yet
> 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.
[jira] Resolved: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SM-1726.
------------------------------
Resolution: Fixed
Fix Version/s: 3.2.4
3.3.1
servicemix-cxf-bc-2008.02
> 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
> Fix For: servicemix-cxf-bc-2008.02, 3.3.1, 3.2.4
>
>
> 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.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48274#action_48274 ]
Ron Gavlin commented on SM-1726:
--------------------------------
Hi Freeman,
I would think the cxf-bc consumer "transactional" code should look much like the smx-jms code since both use Spring JMS underneath. I agree that the CXF server w/Spring JMS underneath should be responsible for explicitly managing the transaction.
Your task list looks correct to me.
It would be great if you could make the wsdl-only configuration work in smx-cxf-bc consumer w/out requiring explicit Spring configuration.
/Ron
> 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.
[jira] Issue Comment Edited: (SM-1726) Develop test case to
demonstrate and verify that smx-cxf-bc consumer endpoint with transactional
JMS transport sends transactional exchange correctly
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48174#action_48174 ]
njiang edited comment on SM-1726 at 12/15/08 12:13 AM:
-------------------------------------------------------------
I just added an example(System unitest org.apache.cxf.systest.jms.tx) to show how does the JMSTransport work with spring transaction framework for CXF-180, please check latest CXF trunk for it.
was (Author: njiang):
I just add an transaction example(System unitest org.apache.cxf.systest.jms.tx) for CXF-180, please check latest CXF trunk for it.
> 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.
[jira] Commented: (SM-1726) Develop test case to demonstrate and
verify that smx-cxf-bc consumer endpoint with transactional JMS transport
sends transactional exchange correctly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48330#action_48330 ]
Freeman Fang commented on SM-1726:
----------------------------------
commit
http://svn.apache.org/viewvc?rev=729387&view=rev for servicemix-cxf-bc component project
> 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.