Re: [platform-vcm-dev] Team + Refactoring (cont.)

["Bryan Stephenson" <Bryan.Stephenson@xxxxxxxxxx>]

In Java Refactoring, say in the case of a rename, there is a pre pass in
which read only status of resources to be modified is
determined.   If resources to be modified are "read-only" the operation
cannot proceed and the errror dialog is presented.

Is this purely a file-system test of the resource status or are the validate
edit/save hooks invoked at this point?   In a pessimistic locking
environment, the normal state of local files is read-only and explicit
checkouts have to be done to make them writable.    If the hooks are not
invoked in this pre check, then the user will have to manually do a blanket
checkout (nasty) or check out each read-only file individually.

I can see that the hooks will be called before an actual edit/save but is
this true in the case of the preview.


Bryan Stephenson