I suggest to use DataContext.invalidateObjects() to restore the
object state after OptimisticLockingFailure. This will of course
override all uncommitted changes on those objects, but this may be
exactly what you want.
Andrus
On Apr 19, 2007, at 6:29 PM, Ayhan Kondoz wrote:
Hi,
i have
Hi,
i have a problem with refreshing of cached objects.
I do something like this:
SelectQuery query = new
SelectQuery(de.freenet.cayenne.kontingent.Customer.class,
Expression.fromString("cid = " + cid));
List list = context.performQuery(query);
2007/4/18, jerome moliere <[EMAIL PROTECTED]>:
2007/4/17, Michael Gentry <[EMAIL PROTECTED]>:
>
> This isn't really an answer to your question, but could help you. If
> your
> schemas are the same in db1 and db2, I would set up a shared data map
> and
> then copy it into the db1 and db2 data
I just committed the fix to 1.2 and 2.0 branches:
https://issues.apache.org/cayenne/browse/CAY-778
3.0 is not affected, as it is built with Maven. Current 3.0 manifest
looks like this:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: andrus
Build-Jdk
2007/4/19, Peter Schröder <[EMAIL PROTECTED]>:
hi,
i am currently investigating the use of cayennes cross jvm caching with
jgroups, shown here
http://cayenne.apache.org/doc12/object-caching.html
and here
http://cayenne.apache.org/doc12/configuring-caching-behavior.html
my question is, if it is
hi,
i am currently investigating the use of cayennes cross jvm caching with
jgroups, shown here
http://cayenne.apache.org/doc12/object-caching.html
and here
http://cayenne.apache.org/doc12/configuring-caching-behavior.html
my question is, if it is possible to implement a cross-jvm counter, that