Hello Thomas,
Is X an EntityProxy or a ValueProxy? If it's a ValueProxy, then this is the expected behavior; you'll have to either:
It's a ValueProxy (X is not an entity).
Are you sure that an IllegalArgumentException with no message coming from a native method I didn't call directly is an expected behavior?
Shouldn't the framework just let the value defined in the constructor of the domain object, or, if that's too complicated, try raising a better exception?
- set the property value to Boolean.FALSE on the client-side
I went for that one. You're right that it could be boolean though. It's just that in this project every domain property is a Boolean, never a boolean.
Also, I must declare the property in the proxy because, although the Editor I mention doesn't care about it, there are some points where I need to read the value of this property in the client-side.
Thank you very much for the quick answer.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/CL4W_SIVMhYJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment