| Thank you VERY much... I'll use it right away!! :-D
On Feb 19, 2010, at 2:07 PM, Kieran Kelleher wrote: http://issues.objectstyle.org/jira/browse/WONDER-478On Feb 19, 2010, at 11:44 AM, Kieran Kelleher wrote: Because ERXLongResponseTask, which I don't use, uses auto lock/unlock, just like a request thread.
That code is useful for plain old java task Threads that implement Callable or Runnable and do not extend ERXLongResponseTask. It is also useful for any other time you don't want an autolocking EC, perhaps for lazily initialization of an EO in the database in a business logic method where there is no guarantees that you can assume you are in a request thread with autolocking.
I will make a patch and see if someone with commit rights can apply it.
Regards, Kieran
On Feb 19, 2010, at 10:21 AM, John Huss wrote: So why don't we add that code (or something similar) to ERXLongResponseTask.DefaultImplementation?
John
On Thu, Feb 18, 2010 at 6:02 AM, Kieran Kelleher <email@hidden> wrote:
Really, just paste the few lines of code I gave u yesterday into a file and name it MyEOUtils.java, and then change your code below to use the static factory method to create the 'manual locking' ec.
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
|