Hi,
We have a project which uses a Spring design by contract web service
to manipulate EOF objects in a database. The app is packaged into a
WAR and deployed in tomact. We've used ERXEC.newEditingContext() to
create editing contexts to edit the data. We need to be sure that the
editing context is being locked so that the application will handle
concurrency properly.
These are the ERXEC settings in the properties file:
er.extensions.ERXApplication.useEditingContextUnlocker=true
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
er.extensions.ERXEC.useSharedEditingContext=false
er.extensions.ERXEC.defaultCoalesceAutoLocks=true
er.extensions.ERXEnterpriseObject.applyRestrictingQualifierOnInsert=true
We also have these set to enable debugging of auto locking
log4j.logger.er=INFO
log4j.logger.er.extensions.ERXEC.LockLogger=DEBUG
It appears from the logs that are generated that ERXEC is locking
before select and update but not before insert. Is this correct
behavior?
How does ERXEC know when to lock and unlock the editing context?
Does the Request-response loop interact with ERXEC's auto locking in
any way?
--
Regards,
Richard Stephens
Ph: 07 3136 3426
Mob: 0410 111 570
Email: rich...@rjst.com.au
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
