Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Object Sharing Between Java Activities and Advice Implementation : User Scenarios

User Scenarios
This section summarises basic supported and unsupported user scenarios. Table 6 and Table 7 shows the user scenarios for activities and advices with implementations.
Figure 22 Basic User Scenario
Following is the basic user scenario as shown in Figure 22 .
Activity A and Activity B are supported Java Activities
A1 and A2 are Advices (with Implementations) applied on Activity A and Activity B respectively
Activity A and Advice A1 will check-in JAVA objects.
Activity B and Advice A2 can check-in and check-out JAVA objects.
Activity A Check-in
Activity B Check-out
Activity A Check-in
Advice A2 Check-out
Activity A Check-in
Activity B Check-in
obj1 is replaced by obj2 in the map.
Activity A Check-in
Advice A2 Check-out
Table 7 shows the supported and unsupported scenarios for Advices with implementations.
Advice A1 Check-in
Activity B Checkout
Advice A1 Check-in
Advice A2 Checkout
Advice A1 Check-in
Advice A2 Check-in
obj1 is replaced by obj2 in the map.
Advice A1 Check-in
Activity B Check-in
Summary
Any other advice implementation or supported JAVA activity with the knowledge of this unique key can check-out that object.
Limitations
When an object is checked-in with a unique-key and the same unique-key is used to check-in a different object, it is only supported provided the original entity that checked-in the object is of the same type. For example, an advice implementation can overwrite an object checked-in by another advice implementation but NOT by an activity.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved