Creating context and changing data value
The following scenarios focus on context creating and data value
changing. These scenarios happen in scenes like establishing a session when
a user logon, and perform the first step of a transaction.
- Scenario I (for Persistence Shared CHA or Memory Shared CHA)
Given that you already have a root Context A:
- Create a remote Context B
- Chain the newly created Context B to the root Context A
- Change the value of Context B using the APIs like setValueAt(), setKeyedCollection()
- Commit the Context B
- Scenario II (for Persistence Shared CHA or Memory Shared CHA)
Given that you already have a root Context A
- Crate a local Context B
- Chain the newly created Context B to Context A
- Change the value of Context B using the APIs like setValueAt(), setKeyedCollection()
- Get the value of Context B using the APIs like getValueAt(), getKeyedCollection()
- Unchain the Context B
- Scenario III (for Persistence Shared CHA or Memory Shared CHA)
Given that you already have a remote Context A:
- Create a remote Context B
- Chain the newly created Context B to the Context A
- Change the value of Context B using the APIs like setValueAt(), setKeyedCollection()
- Commit the Context A
- Scenario IV
Given that you have a remote Context
A:
- Create a local Context B
- Chain the Context B to the Context A
- Change the value of Context B using the APIs like setValueAt(), setKeyedCollection()
- Get the value of Context B using the APIs like getValueAt(), getKeyedCollection()
- Unchain the Context B
- Commit the Context A
- Scenario V (for Persistence Shared CHA, Memory Shared CHA, or Local
CHA)
Given that you already have a local Context A:
- Create a local Context B
- Chain Context B to Context A
- Change the value of Context B using the APIs like setValueAt(), setKeyedCollection()
- Get the value of Context B using APIs like getValue(0, getKeyedCollection()
- Unchain the Context B