Grouper Users - Open Discussion List

["Dr. Loris Bennett" <>]

On Mon, 2009-01-19 at 14:34 -0600, Tom Barton wrote:
> Chris Hyzer wrote:
> >>>> but I don't really understand the consequences of using 
> >>>> READ_WRITE_OR_USE_EXISTING as opposed to READ_WRITE_NEW.
> > 
> > In a web service these are equivalent.  If you were in Java, and you
> > did READ_WRITE_OR_USE_EXISTING, then it would detect if it were
> > already in a transaction context, if so use it, if not, make a new
> > one which is READ_WRITE.  If you did READ_WRITE_NEW, then even if
> > there were an existing transaction, it would create a new autonomous
> > one which didn’t interact with the outer one
> > 
> > 3. In a web service, if there is one operation (e.g. not batched), or
> > if it is batched with size one, then you don’t need to pass any
> > transaction type.  Even if the operation touches many underlying
> > tables (e.g. adding a stem will also create some membership records
> > for who is allowed to edit it), all that will happen in one tx no
> > matter what.  However if it is batched, if you pass READ_WRITE_NEW,
> > then all in the batch will be one tx.  If not passed, or if NONE,
> > then each individual operation will be its own transaction.
> > 
> > Is the Javadoc for 1.4 posted???  In any case, it should be in the
> > binary release, or you can build it with ant.  Look at
> > GrouperTransactionType javadoc:
> 
> 1.4.0 javadoc is linked on the wiki under Grouper Product. It's at
> <http://middleware.internet2.edu/dir/groups/grouper/grouper/1.4.0/doc/api/index.html>.
> 

Is the javadoc for grouperClient also available via the wiki?
-- 
Dr. Loris Bennett (Mr.)
Freie Universität Berlin
ZEDAT - Zentraleinrichtung für Datenverarbeitung / Computer Center
Compute & Media Service
Fabeckstr. 32, Room 221
D-14195 Berlin
Tel ++49 30 838 51024
Fax ++49 30 838 56721
Email 

Web www.zedat.fu-berlin.de