![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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
•
• Activity B and Advice A2 can check-in and check-out JAVA objects.
Table 6 User Scenarios for Activities Activity A Check-in Activity B Check-out obj1 returned by Activity B. Activity A Check-in Advice A2 Check-out obj1 returned by Advice A2. 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 obj1 returned by Activity B. Advice A1 Check-in Advice A2 Checkout obj1 returned by Advice A2. Advice A1 Check-in Advice A2 Check-in obj1 is replaced by obj2 in the map. Advice A1 Check-in Activity B Check-in
• Any other advice implementation or supported JAVA activity with the knowledge of this unique key can check-out that object.
• 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.
• An activity can overwrite an object checked-in by another activity but NOT an advice implementation.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |