Jazz Source Control Pessimistic locking doesn't work?
Hi,
i've installed version 5.0.2, because i want to use the new perssimistic locking feature.
We have one stream and serveral workspaces.
The stream should lock the following filetypes:
.rpgle, .rpg, .pf, .lf, .prtf, .dspf, .clle, .cl
I have done these entries in the new provided text area and saved it.
Now if i open a rpgle file from my workspace, and my colleague opens the same file from his own workspace.
Shouldn't I get now a dialog box with lock read only?
Or how does that feature work?
Accepted answer
It's important that users understand the supported workflow, and there's two basic cases:
Editing in Eclipse
Most Eclipse editor use Eclipse Team API functions to signal that an edit is beginning allowing the current SCM system to intervene, with RTC that means that as soon as the first change is detected then for these automatically locked file types the user will be prompted to lock the file.
Note this means that if no changes are made then the file is not locked by RTC and the file is left as read-only on disk. To initiate the locking procedure a change must be made.
(Note, as mentioned by Shashikant, there are non-conformant editors that may appear in Eclipse but not correctly invoke the Team API, in this case treat the file as if it was edited externally.)
Editing with non-Eclipse Applications
Since non-Eclipse editors have no way to interact with the Team API users must manually lock the "automatically locked" files they wish to edit externally. If the user does not manually initiate the lock then the file is left as read-only through the file system. This means that users will be able to make changes in external applications but unable to save them until a lock is initiated.
Editing in Eclipse
Most Eclipse editor use Eclipse Team API functions to signal that an edit is beginning allowing the current SCM system to intervene, with RTC that means that as soon as the first change is detected then for these automatically locked file types the user will be prompted to lock the file.
Note this means that if no changes are made then the file is not locked by RTC and the file is left as read-only on disk. To initiate the locking procedure a change must be made.
(Note, as mentioned by Shashikant, there are non-conformant editors that may appear in Eclipse but not correctly invoke the Team API, in this case treat the file as if it was edited externally.)
Editing with non-Eclipse Applications
Since non-Eclipse editors have no way to interact with the Team API users must manually lock the "automatically locked" files they wish to edit externally. If the user does not manually initiate the lock then the file is left as read-only through the file system. This means that users will be able to make changes in external applications but unable to save them until a lock is initiated.
2 other answers
Have you looked at https://jazz.net/downloads/rational-team-concert/releases/5.0.2?p=news#pessimisticLocking ?
Comments
>>> No, the files can be edited and saved.
This suggests that the pattern did not get applied/processed during the load. Is the stream the default flow target? The current design only works when the stream is the default flow target.
Another thing to try out is to change the file attributes to read only manually and then try editing or saving the file. This should show the dialog. This is not a solution but to confirm that the dialog shows up.
Comments
showing 5 of 7
show 2 more comments