Support for read-only transaction in xa resource proxy

[arinban]

generic jms ra has a proxy for the XA resource participating in an XA transaction. the proxy controls the transaction state changes in the actual xa resource. So the actual state change may not be propagated back to the resource always. In case of a read-only transactions, the behavior of the Resource proxy needs to be verified. In case of read-only transaction prepare or commit may not be called on the transaction (depending on whethere there is 1 or more resources in the transaction). This situation has to be accounted in the resource proxy, especially during redelivery when the start of a transaction is delayed until prepare is called.

Environment

Operating System: All Platform: Sun

Affected Versions

[v1.6]

[arinban]

• Issue Imported From: https://github.com/ari-ban/test1/issues/29
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented

• Issue Imported From: https://github.com/ari-ban/glassfish-genericjmsra/issues/29
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented

• Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/29
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by rampsarathy

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Was assigned to rampsarathy

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-29

[arinban]

Closing this as this issue is migrated to https://github.com/ari-ban/test1/issues/29