Hi Gustavo,
On 03/08/2008, at 12:37 AM, Gustavo Pizano wrote:
Ok so let's say I have this
try {
session().defaultEditingContext().saveChanges();
} catch (ValidationException e) {
setErrorMsgs(e.getMessage(
On 02/08/2008, at 11:46 PM, Jeff Schmitz wrote:
Hi Dave,
Regarding your comments on ERXEC (which I am using in all my EO's,
or at least all my EO's extend ERXGenericRecord):
I always create new ECs for any task that is going to require
editing.
Using Project Wonder's ERXEC makes this p
Ok so let's say I have this
try {
session().defaultEditingContext().saveChanges();
} catch (ValidationException e) {
setErrorMsgs(e.getMessage());
} catch (EOGeneralAdaptorException e) {
Hi Dave,
Regarding your comments on ERXEC (which I am using in all my EO's,
or at least all my EO's extend ERXGenericRecord):
I always create new ECs for any task that is going to require editing.
Using Project Wonder's ERXEC makes this particularly painless as it
handles the necessary
On 1-Aug-08, at 8:33 PM, Gustavo Pizano wrote:
Hello everyone, I just wanted to ask a noob question. Everywhere I
look I see about the EditingConext, as I know, it function its to
hold instances of the EO's so they can interact each other and so.
in the tutorials and the documentations, they
Hello everyone, I just wanted to ask a noob question. Everywhere I
look I see about the EditingConext, as I know, it function its to hold
instances of the EO's so they can interact each other and so.
in the tutorials and the documentations, they talk most of the part
about the defaultEditingC
