Approach to Ensure Conflict Detection Works Across Passivation/Activation

If you or a client has encountered Bug 10208604 "Conflict Detection Not Working After AM Passivation/Activation", I've posted example # 161 that illustrates a technique to leverage the conflict detection mechanism added for stateless web service row edits (via Enhancement Request 5738772 "Conflict Detection Mechanism Required in ADF BC Service Layer") to solve the problem in a robust way. The solution involves:

  • Using a change indicator attribute (for example, an object version number field that ADFBC can automatically manage for you if you mark it as a 'history column' of type 'version number')
  • Including the change indicator attribute as a hidden field in the page where the row is being edited
Enjoy.

Comments:

Post a Comment:
Comments are closed for this entry.
About
Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today