A little more detail.
So I am using peer ecs. I have 2 pages. A listing page and an update page to
display the EO.
On the listing page, i click on an item, it takes me to the update page and
displays the details of the EO on a ERXWOForm.
//listing page method
public UpdatePost updatePost() {
UpdatePost page = this.pageWithName(UpdatePost.class);
page.setPost(this.aPost);
return page;
}
I make changes and hit submit calling the update page's peer EC saveChanges.
//update page method, execption handling ommitted for clarity
public ERXComponent saveChanges() {
peerEc.saveChanges();
return this.pageWithName('ListingPage');
}
Could the reason be, that peer ECs cannot share EOs across different ECs
thus the changes are not being reflected to the DB? If so, what would be
best in this situation?
Thanks,
Amiel
I change some values on the
On Fri, Feb 20, 2009 at 12:41 PM, amiel montecillo <[email protected]>wrote:
> Positively sure. I am also using ERXEC.newEditingContext() to create a peer
> ec.
>
> Amiel
>
>
> On Fri, Feb 20, 2009 at 12:37 PM, Lachlan Deck <[email protected]>wrote:
>
>> On 20/02/2009, at 3:30 PM, amiel montecillo wrote:
>>
>> I have a problem on an update operation where using a peer EC does not
>>> reflect the changes to the DB. I can see the EOs object instance values
>>> updated before calling ec.saveChanges() but those new values are not
>>> relected on the DB.
>>>
>>> However, if I use session().defaultEditingContext().saveChanges(), the
>>> new
>>> values are reflected in the DB.
>>>
>>> Am I missing something?
>>>
>>
>> Are you sure you're using a peer ec and not a nested ec?
>>
>> with regards,
>> --
>>
>> Lachlan Deck
>>
>>
>
>
> --
> socket error: unable to connect to 127.0.0.1
>
--
socket error: unable to connect to 127.0.0.1
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
