Re: Direct Actions and Sessions
Re: Direct Actions and Sessions
- Subject: Re: Direct Actions and Sessions
- From: Chuck Hill <email@hidden>
- Date: Thu, 27 Nov 2003 13:38:01 -0800
- Organization: Global Village Consulting, Inc.
Yes, always lock. I'd take it even one step further:
Art Isbell wrote:
On 28/11/2003, at 1:59 AM, Colin Clark wrote:
public WOActionResults updateImageTitleAction() {
Integer imageNum =
Integer.parseInt(context().request().stringFormValueForKey("uniqueImage
Number"));
String newTitleForImage =
context().request().formValueForKey("title");
EOEditingContext ec = new EOEditingContext();
ec.lock();
try {
Image = (Image) EOUtilities.objectMatchingKeyAndValue(ec,
"Image", "imageNumber", imageNum);
image.setTitle = newTitleForImage;
Ick! Public instance variables are an abomination. I hope that was
typo...
image.setTitle(newTitleForImage);
Ah... that's better. :-)
ec.saveChanges();
} finally {
ec.unlock();
}
Better safe than deadlocked (unlikely in this case but possible if you
keep the ec around and an exception is raised from saveChanges().
Chuck
}
I've become paranoid about locking all editing contexts but the
session's default editing context. Please correct me if I'm wrong to
suggest the above in this situation.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
Progress is the mother of all problems.
- G. K. Chesterton
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.