Re: Locking/unlocking EditingContexts
Re: Locking/unlocking EditingContexts
- Subject: Re: Locking/unlocking EditingContexts
- From: "Guido Neitzer" <email@hidden>
- Date: Fri, 8 Sep 2006 09:50:31 +0200
Hi.
2006/9/7, Ute Hoffmann <email@hidden>:
EREXEC
It says it needs to be used exclusivlely. Does that mean, that I cannot
have the session.defaultEditingContext in an App using ERXEC?
You can use the session.defaultEditingContext. If you use ERXEC you have to include ERExtensions in your project and this will change a lot ... be aware of that. (Look below for some hints)
How about locking. Do I understand it correctly that ERXEC will set me
free from locking the EditingContext. So I don't have to lock it in
session awake/sleep?
Yes, that's correct. There is a setting for the Properties file to enable / disable autolocking. Look at the Properties file in ERExtensions for the settings.
Will EREXEC require the use of the whole of project wonder - or will
it work on its own?
It's probably the easiest way to include ERExtensions and ERJars and get used to using Wonder. "The whole" thing is quite a bit more stuff. You only need ERExtensions and ERJars and be sure to make your session class a subclass of ERXSession and your application class a subclass of ERXApplication.
You also need to add some settings to your Properties to get logging working as ERExtensions routes logging to log4j.
The other way is to grab the code from ERExtensions for ERXEC's autolocking. But this might be more work, then incorporating Wonder and using it - it helps with a lot of things, not only locking.
cug
--
PostgreSQL Bootcamp, Big Nerd Ranch Europe, Nov 2006
http://www.bignerdranch.com/news/2006-08-21.shtml
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden