[
https://issues.apache.org/jira/browse/AMQ-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved AMQ-59.
----------------------------
Resolution: Won't Fix
Closing old ticks and ideas.
> allow JDBC persistence to be linked with normal JDBC operations to avoid XA
> ---------------------------------------------------------------------------
>
> Key: AMQ-59
> URL: https://issues.apache.org/jira/browse/AMQ-59
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Message Store
> Reporter: james strachan
> Assignee: james strachan
> Priority: Minor
> Fix For: NEEDS_REVIEWED
>
>
> Its a common use case to perform JDBC operations along with JMS and want XA.
> If we're using JDBC persistence for the message store, we could use the same
> JDBC connection and avoid the need for XA.
> To implement this we could
> * use a synchronous VM TransportChannel (currently VMTransportChannel is
> async)
> * let the JDBCMessageStore use the current Connection that the users
> persistence code is using (e.g. using Spring's helper methods or something -
> a custom DataStore provider could hide this
> Then the Connection.commit() could effectively be an XA like commit across
> any persistence code and JMS operations
--
This message was sent by Atlassian JIRA
(v6.1#6144)
