On Mar 12, 3:49 pm, Craig Federighi <craig.federi...@gmail.com
> > Maybe a List of newly created objects could solve the problem, but we
> > could get in to trouble trying to maintain uniquing consistency after
> > querying to the database (what if other user created an object that
> > "matches" the compound id of ours?)
> No matter how you cut it, you'll need a key allocation approach that
> avoids issuing duplicate keys...
> > I would like to try with other JPA providers... do I have to do
> > something other than changing the hibernate jars with
> > EclipseLink or Cayenne jars
> Yes. You'll notice that there's a HibernateContext (subclass of JPA
> context) that implements a few abstract methods in JPAContext -- you'd
> have to do something equivalent for your other implementations.
> > BTW if I want to try with a non JPA compliant API (Cayenne Classic for
> > example), or test the list idea but inheriting from JpaObjectContext
> > instead of messing with Ariba internal code... what would I have to
> > do to register with Ariba a new custom ObjectContext?
> There's some discussion of that topic here: