Re: Custom Entity Classes
Re: Custom Entity Classes
- Subject: Re: Custom Entity Classes
- From: Pascal Robert <email@hidden>
- Date: Mon, 18 Jun 2012 15:54:34 -0400
Le 2012-06-18 à 15:09, Ramsey Gurley a écrit :
>
> On Jun 18, 2012, at 11:42 AM, doug andrews wrote:
>
>> Our app currently does not use any of the Wonder frameworks at all. (It's big and was written over 10 years ago)
>> I'd like to use ERXEC.newEditingContext(), as well as some of the other Wonder goodies.
>> I've never been able to get the ec locking right on my own.
>>
>> I'd like to ease my way into this, so can I start with only using ERXEC.newEditingContext(), and not ERXApplication or ERXSession? (And leave my EOs as EOGenericRecords instead of ERXGenericRecords). Will it still lock properly for me?
>
> No. ERXEC is dependent on other parts of wonder.
>
>> Also, is there a minimum requirement for the version of WO or the version of java if I want to use Wonder?
>> We have several sites still running java 1.4 and WO 5.2.
>
> I believe 1.5 is the current requirement, although I think there's been talk to require 1.6+ after WOWODC this year.
Yes, 1.5 is an absolute since 1.5 things like annotations and generics were added.
>>
>> Also, Ransey mentioned that i cannot pass the ec off into a separate thread. If i only use it to fetch raw rows, is it still a problem?
>
> Not passing an ec/eo to a background thread is due in part to the autolocking used in Wonder. I don't know if there's any restriction of this sort for a non-wonder app. I've never built an app without wonder :-)
>
> Ramsey
> _______________________________________________
> 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
_______________________________________________
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