Rodrigo B. de Oliveira - 05/Jun/07 02:37 PM The separate reference system has strong implications on object identity (the *same logical* object will be exposed as different instances in different _transactions_). I think that alone implies more than a transaction so I would like to use a more heavyweight name, something like Session. It might make sense to use finer grained interfaces for the different sets of functionality in ObjectContainer: interface Queryable {     Query query();     List<T> query<T>(Class<T> extent);     List<Extent> query<Extent>(Predicate<Extent> predicate);     // ...     // other query related methods } interface ObjectSession extends Queryable {     void set(Object o);     void delete(Object o);     void commit();.     void rollback();      } interface ObjectContainer extends ObjectSession {     ObjectSession newSession();     // ...     // ext, configuration, other stuff }

Rodrigo B. de Oliveira - 28/Aug/07 12:16 PM fixing milestone