5 @page EndpointPolicy Test README File
7 This test validates the TAO-specific Endpoint Policy. The Endpoint Policy
8 is applied to a POAManager via the POAManagerFactory, it is not applied to
9 individual POAs. Any POA associated with an endpoint constrained POAManager
10 is subject to the same constraint.
12 The server in this test takes one or more localhost-based -ORBEndpoint
13 arguments. A second argument supplies the "correct" port number to be used
14 to create an Endpoint Policy value. Internally, the server creates an
15 invalid endpoint using the hostname_in_ior option for -ORBEndpoint.
17 Two Endpoint Policy instances are created, one using localhost and the
18 supplied port number, and another creating an invalid endpoint. These are
19 then supplied to the separate POAManagers which are then used to create
20 new POAs. Object references are created on each of the root, good, and bad
23 The client is then passed an IOR and a flag indicating this is expected to
24 succeed or fail. The test succeeds if the client can use the good IOR and
25 gets an exception using the bad IOR.
27 To run the test use the run_test.pl script:
31 Beyond the basic test run using run_test.pl, there are two variants,
32 a localhost based test and a "defaulted host" test. The localhost test
33 uses "localhost" as the hostname rather than allowing the server to
34 get the systems hostname. The Localhost test is not when autorunning
35 on the vxworks platform.
37 To run the localhost test:
41 In the defaulted host test, the hostname argument supplied to the
42 endpoint policy is "". As discussed in Bug #3256, the behavior of
43 using defaulted hosts is changed so that unless more than one
44 protocol are involved, a defaulted hostname is not allowed in the
45 Endpoint Policy value list.
47 The defaulted host test only runs the server program, not the client.