commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Jakarta-commons Wiki] Update of "Brainstorm 2.0" by OliverZeigermann
Date Mon, 12 Mar 2007 11:06:52 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by OliverZeigermann:

New page:
== This page is a collection of ideas for the Commons Transaction 2.0 version. ==

 * as few dependencies as possible (few external jars)
 * require Java 1.5
 * use java.util.concurrent
 * use a different package name (e.g. o.a.j.c.transaction2)
 * maybe supply a 1.x compatibility package
 * only impement a core that does the transactional part
  * leave the rest to optional modules and custion implementations by calling exchangeable
implementation of interfaces
  * use Spring for configuration
  * modules
   * How does a transaction map to temporary data
   * Where is temporary data and final data stored (maybe use VFS?) 
   * Id generator
   * What else?
 * have a default implementation 
  * for all required modules 
  * keept it slim and rudimentary
  * amounts to a transactional file store out of the box

Features of the file implementation:
 * allow for additional guarenteed deadlock free actions on resources
  * move and tree-move
  * copy and tree-copy
  * delete and tree-delete
 * maintain an explicite tree (graph?) structure
Open Questions:
 * Is Jakarta Commons the right place for such a project?
 * Should we introduce threading in order to
 * Allow remote access / administration to a file store
 * Allow for deadlock detection in its own thread
 * what else?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message