git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Any plans to support JTA and XA in jgit?

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Nov 13, 2008, 19:59 UTC
Message-ID
<200811132059.16616.robin.rosenberg.lists@dewire.com>
torsdag 13 november 2008 20:20:49 skrev Farrukh Najmi:
Show 5 quoted lines
> 
> Does the gjit team have any plans to implement support for JTA in gjit 
> so as to allow distributed transactions using 2 phase commit? This would 
> be very powerful when git is being used in conjunction with other 
> transaction resource managers such as databases.

No such plans exist. We do not even have a J2EE Resource Manager yet. I did some toying implementing one. As for XA support, I guess that would not be very hard per se, but my thoughts on JEE support was more in the direction of gitweb-like stuff, i.e. reading.

Trying to involve git in distributed database transactions might be cool, but seriously: Do you need it? As for JEE my ideas are: A nice JSP tag library and a resource manager. When is an entirely different question, as is who. Did you look at my experiment in a reply of mine in another recent jgit thread?

The term "distributed" in XA is not quite the same as in distributed verison control. If it would, then we'd send SQL commands over e-mail (now, /that/ would be cool :).

-- robin
Next: Farrukh Najmi
Message 1 of 8 in “Re: Any plans to support JTA and XA in jgit?”
  1. Robin RosenbergNov 13, 2008
  2. Farrukh NajmiNov 13, 2008
  3. Robin RosenbergNov 13, 2008
  4. Kyle MoffettNov 14, 2008
  5. Farrukh NajmiNov 14, 2008
  6. Any overview available on jgit codebase?Farrukh Najmi, Nov 15, 2008
  7. Shawn O. PearceNov 15, 2008
  8. Farrukh NajmiNov 16, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.