1 files changed, 97 insertions, 0 deletions
diff --git a/TAO/tests/POA/README b/TAO/tests/POA/README
new file mode 100644
index 00000000000..9d4a03425d2
--- /dev/null
+++ b/TAO/tests/POA/README
@@ -0,0 +1,97 @@
+// $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.
+
+        . POA_Destruction
+
+                The program tests the destruction of a POA during an
+                upcall.
+
+        . Default_Servant
+
+                This program tests the behavior of
+                POA::id_to_servant() and POA::reference_to_servant()
+                with the use of default servants.
+
+        . Object_Reactivation
+
+                This program tests the reactivation of a servant that
+                has been deactivated but not removed from the Active
+                Object Map yet.
+
+        . Excessive_Object_Deactivations
+
+                This program tests for excessive deactivations of a
+                servant.  The test checks excessive deactivations in a
+                POA with SYSTEM_ID and other POA with USER_ID.  The
+                test also check for excessive deactivations during
+                upcalls.
+
+        . 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.
+
+        . Etherealization
+
+                This program tests for deactivation and
+                etherealization of reference counted and non reference
+                counted servants.
+
+        . Persistent_ID 
+
+                This test checks the combination of PERSISTENT &
+                SYSTEM_ID POA policies.
+
+        . Policies
+
+                This program tests the construction of POA policies,
+                both through the generic ORB::create_policy interface
+                and the PortableServer specific interfaces.
+
+        . MT_Servant_Locator
+
+                This program tests that multiple calls to the Servant
+                Locator can take place simultaneously.
+
+        . Nested_Non_Servant_Upcalls
+
+                This program tests that nested non-servant upcalls are
+                handled correctly.
+
+        . POAManagerFactory
+   
+                The program tests the POAManagerFactory interface. Test may
+                be run by hand using "POAManagerFactory -v" to get a verbose 
+                report of individual tests being run.
+
+        . EndpointPolicy 
+
+                Tests for the endpoint policy, the server listens on two
+                endpoints, one with an alias rendering it unreachable. The 
+                server uses the endpoint policy to create two IORs, one with
+                the only the good endpoint and another with only the bad. The
+                client expects to reach the good ior and expects to fail with
+                the bad ior.