blob: 21cf7b6b5704404aa34b569184214c2998f84f42 (
plain)
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
// $Id$
The following TAO applications test and illustate various Portable
Object Adapter (POA) interfaces and their usage scenarios.
. Identity
The example shows the identity between servants, ids,
and references.
. Destruction
The program tests the destruction of a POA during an
upcall.
. Deactivation
This program tests the reactivation of a servant that
has been deactivated but not removed from the Active
Object Map yet.
. Non_Servant_Upcalls
This program check the users ability to make calls on
a POA during non-servant upcalls. In this example, a
servant which is being destroyed during because of a
deactivate_object() call, tries to deactivate another
object in its destructor.
. wait_for_completion
This program tests the <wait_for_completion> feature
of the POA.
. Single_Threaded_POA
This program tests to make sure that two threads
cannot call servants in a single threaded POA
simultaneously. At the same time, it makes sure that
a servant can call itself or other servants in the
same POA while in an upcall.
. Multiple_Deactivation
Regression test for:
http://ace.cs.wustl.edu/bugzilla/show_bug.cgi?id=834
The test creates a single object reference and
deactivates it three times in the context of a
request. The servant verifies that the destructor is
not invoked in this context, and that reference
counting rules are properly followed.
|
