You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2008/12/16 10:40:44 UTC

[jira] Resolved: (CXF-180) JMS Transport support for transaction

     [ https://issues.apache.org/jira/browse/CXF-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CXF-180.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2
                   2.1.4
                   2.0.10

Applied the System test into 
trunk
http://svn.apache.org/viewvc?rev=726639&view=rev
2.1.x
http://svn.apache.org/viewvc?rev=726756&view=rev
2.0.x
http://svn.apache.org/viewvc?rev=726948&view=rev

I also kicked a new 2.0.10 snapshot deployment hours ago. 
Rong , you should access it now :)

> JMS Transport support for transaction
> -------------------------------------
>
>                 Key: CXF-180
>                 URL: https://issues.apache.org/jira/browse/CXF-180
>             Project: CXF
>          Issue Type: New Feature
>          Components: Transports
>    Affects Versions: 2.1
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.0.10, 2.1.4, 2.2
>
>
> Here are some points on the JMS Transport stuff:
> [ulhas]
> Currently JMS Session pool in Artix uses different Message Receiver
> acknowledgement mechanism than Celtix to provide Transaction support.
> (Celtix uses AUTO_ACKNOWLEDGEMENT) whereas Artix uses CLIENT_ACKNOWLEDGE
> for server side.
> [Willem]
> AUTO_ACKNOWLEDGMENT just make sure JMS broker client
> received the message, but not sure about the client had processed the message.
> If we want to support the Transaction in CXF, I think we need to change to
> CLIENT_ACKNOWLEDGE to make sure the message had been processed in
> message level.
> [ulhas]
> Second part of the transaction support is in current JMSServerTransport
> postDispatch code. This is the place where the server make sure that the
> message received can be processed and it is safe to send the
> Acknowledgement to JMS broker to remove the message from topic/queue and
> commit.
> [Willem]
> In current CXF JMS Transport implementation the transport just provide an channel
> to send and receive messages. All the message handling stuff need to play with the
> Stream. I think it is a good place in the OutputStream close method to send
> acknowledgment to JMS broker.
> So if we want to support local transaction in CXF JMS, we just need change the Session
> acknowledgment and the OutputStream close method. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.