Re: IllegalStateException: undo: undo manager is in invalid state - Huh?
Re: IllegalStateException: undo: undo manager is in invalid state - Huh?
- Subject: Re: IllegalStateException: undo: undo manager is in invalid state - Huh?
- From: "Paul R. Summermatter" <email@hidden>
- Date: Mon, 28 Apr 2003 16:04:48 -0400
Folks,
I missed the original post on this, but I think I can provide some
comment. <disclaimer>Some of this information may be out of date or
obsolete</disclaimer>. Apple made the decision to wrap any server side
method invocation that comes from the java client into its own undo
grouping so that any failures while handling a request could be cleaned
up before a response is returned to the client. This means that, if
you use the session's default editing context and you want to do your
own cleanup by calling say 'revert' on the ec if something fails, you
will get the exception noted in the subject line. We use the java
client in a very non-standard manner and are able to get around this
issue by using our own private EC for making changes to objects based
on client requests. It may be that WO 5.2 has changed the picture
somehow, but I haven't re-tested.
Regards,
Paul
On Monday, April 28, 2003, at 03:43 PM, Chuck Hill wrote:
I'm not very familiar with JC, but if you can set the EC on the server
(e.g. with session().setDefaultEditingContext() or something like
that) you could use a sub-class which overrides saveChanges() and does
this. That is what I use for web apps.
FWIW
Chuck
Nick Pilch wrote:
I'm not sure how this would work in a Java Client app. A call to
EOEditingContext.saveChanges() on the client probably invokes a
saveChanges() on the server, but it all happens behind your back.
At 2:28 PM -0700 4/25/03, Chuck Hill wrote:
another thing to try is to call
editingContext().undoManager().removeAllActions() after a successful
saveChanges().
Chuck
At 02:09 PM 25/04/2003 -0700, Nick Pilch wrote:
I can't help you with the source of the problem, but I can
sympathize. My users get this very occasionally, and I have no idea
why.
I do know this: EOEditingContexts use an undo manager, so what
you're
seeing is most likely an internal WO problem. I've tried setting the
undo manager for my java client's session's default editing context
on the server to null (or the levels of undo to 0 - I can't remember
which), but I got a warning on the console from WO that it
definitely
needed the undo manager to function correctly for Java Client stuff.
--
Nick Pilch / email@hidden
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
Progress is the mother of all problems.
- G. K. Chesterton
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.