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