Re: ERXEC question

2013-08-12 Thread John Huss
No, what you described is the standard behavior. Wonder (ERXEC) provides a way to include the unsaved changes if you desire, but this is not the default/standard. On Mon, Aug 12, 2013 at 2:31 PM, Lars Sonchocky-Helldorf < lars.sonchocky-helld...@xyrality.com> wrote: > So you're suggesting that

Re: ERXEC question

2013-08-12 Thread Dev WO
I haven't check the "normal" EC management, but I'm pretty confident that if it's not the default behavior in Wonder it's because it could be "unsafe". Xavier On 12 août 2013, at 21:31, Lars Sonchocky-Helldorf wrote: > So you're suggesting that the behavior we are seeing here is specific to

Re: ERXEC question

2013-08-12 Thread Lars Sonchocky-Helldorf
So you're suggesting that the behavior we are seeing here is specific to ERXECs and not to "normal" ECs? cheers, Lars Am 12.08.2013 um 21:26 schrieb Dev WO : > Hi Lars, > > You could overwrite (or create another) method "fetchAllPaymentCustomers" to > apply: > setIncludeEditingContex

Re: ERXEC question

2013-08-12 Thread Dev WO
Hi Lars, You could overwrite (or create another) method "fetchAllPaymentCustomers" to apply: setIncludeEditingContextChanges(true) I recall a discussion about this stating it was "on purpose" that Wonder doesn't do it by default. So you have to manually deal with it that way you actually know

Re: ERXEC question

2013-08-12 Thread Ramsey Gurley
You can use an ERXFetchSpec to include objects that only exist in the EC. I believe there's a bug in that which causes duplicate EOs to show up when using nested ECs though. On Aug 12, 2013, at 10:37 AM, Lars Sonchocky-Helldorf wrote: > Hi list, > > we are creating a new EO and insert it into

ERXEC question

2013-08-12 Thread Lars Sonchocky-Helldorf
Hi list, we are creating a new EO and insert it into an ERXEC like this: public static PaymentCustomer createPaymentCustomer(EOEditingContext editingContext, Integer creditScore, String fullQualifiedClassName, Integer ingameId) { PaymentCustomer eo = (PaymentCustomer) EOUtilities.crea

Re: ERXEC question

2008-08-04 Thread Guido Neitzer
On 04.08.2008, at 15:57, Lachlan Deck wrote: extend ERXApplication extend ERXSession use ERXEC.newEditingContext() All true. But: Properties: er.extensions.ERXApplication.useEditingContextUnlocker=true er.extensions.ERXEC.defaultAutomaticLockUnlock=true er.extensions.ERXEC.useSharedEditingCo

Re: ERXEC question

2008-08-04 Thread Lachlan Deck
On 05/08/2008, at 9:40 AM, Gustavo Pizano wrote: Hello, I paste this lines on my properties file: extend ERXApplication extend ERXSession use ERXEC.newEditingContext() the other ones were there already Yep - just restating the normal steps for getting going. so now what should I do if I d

Re: ERXEC question

2008-08-04 Thread Lachlan Deck
On 05/08/2008, at 1:24 AM, Gustavo Pizano wrote: Well I have a component which was using the session defaultEditingContext, so what I did was that I create an instance variable in that component of ERXEC, then I replace the displayBoard = (DisplayBoard) EOUtilities .createAndInsertInstance

Re: ERXEC question

2008-08-04 Thread Guido Neitzer
On 04.08.2008, at 09:24, Gustavo Pizano wrote: Why that error came up?, what does it means the coalesce auto- locks, ? It means, it locks on the first access and let the automatic unlocker take care of unlocking it. You don't have that set to true in your properties. and third, did I

ERXEC question

2008-08-04 Thread Gustavo Pizano
hello all. Well I have a component which was using the session defaultEditingContext, so what I did was that I create an instance variable in that component of ERXEC, then I replace the displayBoard = (DisplayBoard) EOUtilities.createAndInsertInstance(session().defaultEditingContext(), "