Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-23 Thread Thomas Broyer
On Monday, April 23, 2012 10:29:35 AM UTC+2, Tiago wrote: Hello Brandon, My problem isn't always autobean is frozen, it changes, but the summary is that I cannot resubmit a proxy after a server error (like an unique constraint violation, for example) that ends up calling

Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-23 Thread Tiago
Hello Thomas, On Monday, April 23, 2012 11:49:54 AM UTC+2, Thomas Broyer wrote: In RequestFactory's design, onFailure is really an exception, and should never happen: errors should be conveyed as special return values. That doesn't quite change your issue here, as the proxy wouldn't be

Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-23 Thread Thomas Broyer
On Monday, April 23, 2012 2:57:09 PM UTC+2, Tiago wrote: Hello Thomas, On Monday, April 23, 2012 11:49:54 AM UTC+2, Thomas Broyer wrote: In RequestFactory's design, onFailure is really an exception, and should never happen: errors should be conveyed as special return values. That

Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-23 Thread Tiago
On Monday, April 23, 2012 4:21:50 PM UTC+2, Thomas Broyer wrote: You can use a custom JSR303 validator that does the select and the check; so that in case of a unique constraint violation, a ConstraintViolation would be sent back to the client (and in this case, the proxy is unfrozen so it

Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-21 Thread Brandon Donnelson
I've has those too. I'm not sure there is enough source to diagnose. Do you have a list in your bean? 1. how do you init your driver? 2. do you have list that is null from server. 3. do you have a list that is null when you start then you add to list then edit it again. always init a list as

Re: RequestFactory/Editor AutoBean has been frozen error

2012-04-19 Thread Tiago Rinck Caveden
Hello all, I tried to reply to the message below in its own thread (here: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/4309e1e60f2cb8d8?pli=1 ), but I was getting an error at every attempt, so I decided to open a new topic with the same title. It seems this useful

Re: RequestFactory/Editor AutoBean has been frozen error

2011-12-09 Thread Thomas Broyer
It's by design, so nothing has changed in 2.4; and http://code.google.com/p/google-web-toolkit/issues/detail?id=5794 hasn't yet been fixed (patches welcome! ;-) ). -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on

Re: RequestFactory/Editor AutoBean has been frozen error

2011-12-08 Thread bloo
Hi, I'm glad I found this thread as I've run into the same pattern. Is the AutoBean hack on onFailure still required, as of 2.4.0? Or is there a more elegant control to be able to reuse the RequestContext and EntityProxy? -- You received this message because you are subscribed to the Google

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-22 Thread Scott Olcott
Thomas, You are correct in understanding my issue. I tried calling AutoBean.clone(), but is fails with a Cannot clone wrapped bean error. I was however able to resubmit the proxy successfully using the following: AutoBeanTest autoBean = AutoBeanUtils.getAutoBean(test);

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-20 Thread Thomas Broyer
On Sunday, February 20, 2011 3:26:35 AM UTC+1, Colin Alworth wrote: I think you are addressing the wrong issue – Scott is pointing out that general exceptions do not allow you to re-fire contexts after modifying the proxies further. Given his last message, about clearing 'invocations'

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-19 Thread Colin Alworth
I think you are addressing the wrong issue – Scott is pointing out that general exceptions do not allow you to re-fire contexts after modifying the proxies further. The r/o proxy instance is stuck as read only because there still exists a context-specific edited copy of it, which did not

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-18 Thread Scott Olcott
I have temporarily fixed this by copying AbstractRequestContext into a super-source directory and making the change there. I also had to call invocations.clear() to avoid duplicate invocations the next time a request is fired. You also need to make sure editedProxies.clear() is not called

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-18 Thread Thomas Broyer
I think it was on-purpose: validation is done before any invocation is processed, so you can safely send the same invocations back to the server after making changes to the proxies so they validate the next time. I guess the idea is that you then only change proxies and fire the context again,

RequestFactory/Editor AutoBean has been frozen error

2011-02-17 Thread Scott Olcott
I am trying to use the RequestFactory and Editor frameworks together. I have it working successfully for requests that finish successfully or that result in constraint violations. However, whenever there are server errors and my Receiver.onFailure(ServerFailure) method is called I am not able to

Re: RequestFactory/Editor AutoBean has been frozen error

2011-02-17 Thread Scott Olcott
I am using GWT 2.2 On Feb 17, 3:39 pm, Scott Olcott scottolc...@gmail.com wrote: I am trying to use the RequestFactory and Editor frameworks together. I have it working successfully for requests that finish successfully or that result in constraint violations.  However, whenever there are