Project

General

Profile

Bug #877

Lacking support of custom Transaction Managers

Added by Henning Blohm about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
z2-base
Target version:
Start date:
20.08.2012
Due date:
% Done:

0%

Estimated time:
origin:

Description

Currently the TM integration is actually Jetty specific. It should be simple to integrate any transaction manager simply as a
component declaration.

Suggestions:

a) The "java:" JNDI scheme is owned by JEE, e.g. Jetty, Tomcat. We do not intercept to bind - rather bind on the web app level via reference
b) Transaction Manager as well as User TX can be looked up via JNDI component lookups with ?type= params.

Solve this issue in conjunction with a comprehensive Hibernate+Jetty/Tomcat example and #868

#1

Updated by Henning Blohm about 8 years ago

  • Assignee set to Henning Blohm
  • Target version set to 3
#2

Updated by Henning Blohm about 8 years ago

  • Target version changed from 3 to 2.1
#3

Updated by Henning Blohm about 8 years ago

  • Status changed from New to In Progress
#4

Updated by Henning Blohm about 8 years ago

  • Category set to z2-base
#5

Updated by Henning Blohm about 8 years ago

  • Status changed from In Progress to Resolved

Removed the "java:" override.

Provided samples on how to use Atomikos in plain Java apps and Atomikos with Hibernate and Spring.

There will be no particular JTA support beyond the simple pseudo-distributed com.zfabrik.jta.

#6

Updated by Henning Blohm about 8 years ago

See also #877

#7

Updated by Henning Blohm about 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF