[
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.
