> Oh, and the push changes thing appears to be controlled by a property. It > appears that if you want to turn it on you would put > > er.extensions.ERXValidationShouldPushChangesToObject=true > > In your properties file.
It doesn't seem to work for me. Even though I turn it on, a model based exception due to non null field that has been left empty doesn't get pushed. I'm not sure to grasp all the flow of it, but for what I see the push setting acts when an old NSValidation.ValidationException gets converted through the ERXValidation class. Backstepping the validation the main point where this could happen but doesn't (in my particular case) looks like ERD2WPage. The code checks for "e instanceof ERXValidationException" and since it's already the case, no call to ERXValidation is made and so no "pushing" is honored. I can obviously call it myself... but is there a more appropriate way? Anjo? rdm _______________________________________________ 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]
