I just added a couple protected methods to the OM's to allow for some
preprocessing prior to saving the object. The simple one is a doPreSave
method which has an empty default implementation, but provides a hook to
allow pre-processing by the om. The second one involves more classes
and needs to be turned on with the secureSaveMethod property. It
modifies the save methods so that they take an
object implementing the SecurityInfo interface. It also adds a
protected method securityCheck that calls the hasPermission method on
SecurityInfo. If the test fails a SecurityException is thrown and
doPreSave and the rest of the save operations will not occur. Since
Persistent had just had the save methods added, I extended the interface
and moved the save definitions to the children. Any comments or
suggestions for improvement?
john mcnally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
