[IOTDM-26] State Tags don't update properly Created: 24/Aug/15 Updated: 15/May/17 Resolved: 15/May/17 |
|
| Status: | Resolved |
| Project: | iotdm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Lionel Florit | Assignee: | Juraj Kosmel |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4176 |
| Priority: | High |
| Description |
|
When a subscription resource is created under a container resource, the state tag in the container resource does not increment. Note that creating contentInstance does increment the stateTag Example below shows a container resource with 3 contentInstances and 2 subscriptions. Its state tag is =3, should be =5 { "cni": 3, "mni": 10, "ty": 3, "cr": "//localhost:10000", "cbs": 24, "rn": "/ODL-oneM2M-Cse/TestAE/TestContainer", "lbl": [ "key1" ], "or": "http://hey/you", "mbs": 30, "ri": "/ODL-oneM2M-Cse/b", "st": 3, "lt": "20150824T173328Z", "pi": "/ODL-oneM2M-Cse/a", "ct": "20150824T165418Z" } , , , , , { "con": "My Data2", "ty": 4, "rn": "/ODL-oneM2M-Cse/TestAE/TestContainer/TestContentInstance2", "ri": "/ODL-oneM2M-Cse/d", "lt": "20150824T165524Z", "st": 2, "pi": "/ODL-oneM2M-Cse/b", "ct": "20150824T165524Z", "cs": 8 } |
| Comments |
| Comment by Cangji Wu [ 15/Sep/15 ] |
|
According to TS-0001,John and I decide that: Only when create <ContentInstance> should increment st. |
| Comment by Trapti Khandelwal [ 16/Sep/15 ] |
|
Hello Cangji Wu, Following behaviour is being oberserved while replicating the bug : 2 : Upon creation of 3 contentInstance the state tag value is increased to 3 (Correct). 3: {* create contentInstance } In above Scenario the state tag value is increasing normally by 1 for each contentInstance. So for 2nd scenario there is a need to fix the bug. Please confirm If it is to be solved,I will be looking into the code. |
| Comment by Juraj Kosmel [ 27/Apr/17 ] |