Fixed fuzz

25 files changed, 65 insertions, 71 deletions

diff --git a/TAO/tests/Abstract_Interface/README b/TAO/tests/Abstract_Interface/README
index f4607cafe2a..68542087175 100644
--- a/TAO/tests/Abstract_Interface/README
+++ b/TAO/tests/Abstract_Interface/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Description:
 
@@ -22,7 +22,7 @@ directly on the abstract interface by the client. Then the interface
 itself is extracted and cast to the derived type. Finally, both the
 base class and the derived class operations are called by the client.
 
-In the final test, an operation called on the abstract interface 
+In the final test, an operation called on the abstract interface
 is made to throw a user exception deliberately to test exception
 handling.
 
@@ -45,5 +45,5 @@ Other client command line options:
 -e Test exception handling only
 
 The last three options are  mutually exclusive and will override
-any previous test selection options. The default behavior is to run 
+any previous test selection options. The default behavior is to run
 all three tests.
\ No newline at end of file
diff --git a/TAO/tests/BiDirectional_NestedUpcall/README b/TAO/tests/BiDirectional_NestedUpcall/README
index c40ad7424fd..dffdad1bd9c 100644
--- a/TAO/tests/BiDirectional_NestedUpcall/README
+++ b/TAO/tests/BiDirectional_NestedUpcall/README
@@ -1,7 +1,7 @@
-# $Id$
+$Id$
 
 This test is similar to the $TAO_ROOT/tests/BiDirectional test. The
 only difference being that the server as a part of the upcall sends a
-bunch of remote calls, to show some nested upcall behaviour. 
+bunch of remote calls, to show some nested upcall behaviour.
 
 
diff --git a/TAO/tests/Bug_2243_Regression/README b/TAO/tests/Bug_2243_Regression/README
index b44e9b0bae8..683bd294df1 100644
--- a/TAO/tests/Bug_2243_Regression/README
+++ b/TAO/tests/Bug_2243_Regression/README
@@ -1,6 +1,8 @@
+$Id$
+
 This test contains regression tests for fixes to bug #2243
 
     ORB::object_to_string() returns NULL
 
-See the bugzilla record for details. This test is derived 
+See the bugzilla record for details. This test is derived
 from, and based upon, the ORB_init test.
diff --git a/TAO/tests/Bug_2593_Regression/README b/TAO/tests/Bug_2593_Regression/README
index 8da60d5bbb4..9d68a5e6461 100644
--- a/TAO/tests/Bug_2593_Regression/README
+++ b/TAO/tests/Bug_2593_Regression/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page Bug 2593 Regression Test README File
 
 This test is used to demonstrate that TAO can successfully connect
@@ -7,7 +9,7 @@ with a server even if the server's IOR contains profiles the client
 doesn't know about.
 
 When TAO 1.5.2 was released it was discovered that TAO could no longer
-tolerate unknown profiles. This test is designed to ensure that 
+tolerate unknown profiles. This test is designed to ensure that
 problem is caught before another release is cut.
 
 
diff --git a/TAO/tests/Bug_3514_Regression/README b/TAO/tests/Bug_3514_Regression/README
index c3421fb54e2..c9b0e298a96 100644
--- a/TAO/tests/Bug_3514_Regression/README
+++ b/TAO/tests/Bug_3514_Regression/README
@@ -1,5 +1,5 @@
-# $Id$
+$Id$
 
-This is a compile only test. If it compiles, it's passed. 
+This is a compile only test. If it compiles, it's passed.
 
 
diff --git a/TAO/tests/Bug_3558_Regression/README b/TAO/tests/Bug_3558_Regression/README
index 9c57d7f4d03..0bf974fa4d4 100644
--- a/TAO/tests/Bug_3558_Regression/README
+++ b/TAO/tests/Bug_3558_Regression/README
@@ -1,18 +1,20 @@
 /**
 
+$Id$
+
 @page Bug_3558_Regression Test README File
 
 	Test written for Bugzilla #3558
-  
+
   This test is based on the Hello TAO test.
-	
+
   The goal of writing this test is:
 
-- Provide a way to test whether transport cache behaves correctly. 
+- Provide a way to test whether transport cache behaves correctly.
   ORBConnectionCacheMax is programmatically set to 1. When a second
   connection is esthablished, we expect an exception. However, it seems that
-  the transport cache adjusts itself (no exception is thrown). 
-	
+  the transport cache adjusts itself (no exception is thrown).
+
 	To run the test use the run_test.pl script:
 
 $ ./run_test.pl
@@ -22,5 +24,5 @@ or, with debug information:
 $ ./run_test.pl -debug
 
 	the script returns 0 if the test was successful.
-  
+
 */
diff --git a/TAO/tests/Bug_3567_Regression/README b/TAO/tests/Bug_3567_Regression/README
index 04117a71d7d..40368fbdc4a 100644
--- a/TAO/tests/Bug_3567_Regression/README
+++ b/TAO/tests/Bug_3567_Regression/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Description:
 This is a simple test for AMI callback model.
@@ -8,7 +8,7 @@ Use TAO_HAS_CORBA_MESSAGING
 and TAO_HAS_AMI_CALLBACK
 to compile TAO. This enables the AMI code in it.
 
-Use -GC on the TAO IDL compiler to generate code for AMI callbacks. 
+Use -GC on the TAO IDL compiler to generate code for AMI callbacks.
 
 Usage:
 =====
diff --git a/TAO/tests/Bug_3598a_Regression/README b/TAO/tests/Bug_3598a_Regression/README
index b2d570b8158..343f8b57a61 100644
--- a/TAO/tests/Bug_3598a_Regression/README
+++ b/TAO/tests/Bug_3598a_Regression/README
@@ -2,7 +2,7 @@ $Id$
 
 This test attempts to contact a server IOR with no connectable profile in it (on account of how there is no server running).
 
-The method invocation should fail but the installed client request interceptor should have its send_request and receive_exception methods invoked regardless. 
+The method invocation should fail but the installed client request interceptor should have its send_request and receive_exception methods invoked regardless.
 
 The expected result looks like:
 
diff --git a/TAO/tests/Connect_Strategy_Test/README b/TAO/tests/Connect_Strategy_Test/README
index 06be22c2caa..2f8603f8fed 100644
--- a/TAO/tests/Connect_Strategy_Test/README
+++ b/TAO/tests/Connect_Strategy_Test/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page Connect_Strategy Test README File
 
 	The simplest possible test for connection strategies in TAO.
@@ -8,7 +10,7 @@ be argued that it is in fact too simple to make any conclusions based
 on the results from this test.
 
 	Please refrain from "improving", extending or expanding this
-test, if you need to change 
+test, if you need to change
 
 	To run the test use the run_test.pl script:
 
diff --git a/TAO/tests/Connection_Purging/README b/TAO/tests/Connection_Purging/README
index 8f8ec152c3b..a3306694e07 100644
--- a/TAO/tests/Connection_Purging/README
+++ b/TAO/tests/Connection_Purging/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Connection Purging
 ------------------
@@ -12,7 +12,7 @@ Usage: run_test.pl [-u | -s]
 
 There are four configurator files, one for each strategy.  Each configurator
 file sets the -ORBConnectionCacheMax to 10 and the
--ORBConnectionCachePurgePercentage to 30 (excluding client.null.conf). 
+-ORBConnectionCachePurgePercentage to 30 (excluding client.null.conf).
 After 10 separate connections are made, 30% of the transport cache is
 purged in a way that corresponds to the chosen purging strategy.
 
diff --git a/TAO/tests/DII_Collocation_Tests/oneway/README b/TAO/tests/DII_Collocation_Tests/oneway/README
index c5f2ba9d1e9..2720f2002e4 100644
--- a/TAO/tests/DII_Collocation_Tests/oneway/README
+++ b/TAO/tests/DII_Collocation_Tests/oneway/README
@@ -10,12 +10,10 @@ conversion of the DII parameters in NVList to the list of arguments.
 It also defines the operations with multiple "IN" arguments to test the
 bug fix.
 
-
 This test is a modification of the Collocation_Tests. The big difference is
 this test invokes the oneway operations using DII while the Collocation_Tests
 invoke a simple twoway operations.
 
-
 Usage:
 =====
 
diff --git a/TAO/tests/DSI_Gateway/README b/TAO/tests/DSI_Gateway/README
index aad5b8f69e1..68c1d37a9a8 100644
--- a/TAO/tests/DSI_Gateway/README
+++ b/TAO/tests/DSI_Gateway/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 	A simple test for the DSI/DII gateway support. TAO can
 optimize some demarshaling/marshaling and data copying in the
@@ -7,7 +7,7 @@ also pass requests and replies that are not in native (the
 gateway's) byte order. NOTE - For this last feature to work, you
 must compile ACE with ACE_ENABLE_SWAP_ON_WRITE defined.
 
-	This is a smoke test and simple example for those 
+	This is a smoke test and simple example for those
 features. Use
 
         $ server -o server.ior
@@ -25,11 +25,11 @@ then calling a method that raises a CORBA system exception.
         To run these tests by hand, start the server and gateway
 as shown above, then use
 
-        $ client -k file://gw.ior -u 
+        $ client -k file://gw.ior -u
 
 for the user exception test and
 
-        $ client -k file://gw.ior -s 
+        $ client -k file://gw.ior -s
 
 for the system exception test. For these tests, the -x
 option (server shutdown) and -i option (# of calls)
diff --git a/TAO/tests/ForwardUponObjectNotExist/README b/TAO/tests/ForwardUponObjectNotExist/README
index c6ad499922b..1893326c217 100755
--- a/TAO/tests/ForwardUponObjectNotExist/README
+++ b/TAO/tests/ForwardUponObjectNotExist/README
@@ -7,15 +7,15 @@ $Id$
 	This is test for feature of request forwarding when client receives
 	OBJECT_NOT_EXIST exception. The feature is enabled and disabled by
 	-ORBForwardInvocationOnObjectNotExist [0|1] option.
-	
-	The servant implementation is made to raise OBJECT_NOT_EXIST exception. 
-	This is	to simulate the server exception reply regardless the actual 
-	meaning of the OBJECT_NOT_EXIST exception. The test also takes advantage 
+
+	The servant implementation is made to raise OBJECT_NOT_EXIST exception.
+	This is	to simulate the server exception reply regardless the actual
+	meaning of the OBJECT_NOT_EXIST exception. The test also takes advantage
 	of the IORTable facilities in TAO to create a simple corbaloc IOR, TAO
-	always responds with a LOCATION_FORWARD message when a request is 
+	always responds with a LOCATION_FORWARD message when a request is
 	made for an object in the IORTable. This would make the stub have the
 	forward address upon receiving OBJECT_NOT_EXIST exception so it can
-	perform the forwarding. If client runs with the feature disabled 
+	perform the forwarding. If client runs with the feature disabled
 	(-ORBForwardInvocationOnObjectNotExist 0) then the client should catch
 	the OBJECT_NOT_EXIST exception, otherwise, the request will be looping
 	between server and client and the invocation never ends. The invocation
diff --git a/TAO/tests/IDL_Test/README b/TAO/tests/IDL_Test/README
index 9165d90c57e..5f5dce0ab93 100644
--- a/TAO/tests/IDL_Test/README
+++ b/TAO/tests/IDL_Test/README
@@ -1,17 +1,4 @@
-// $Id$
-
-// ============================================================================
-//
-// = LIBRARY
-//    TAO/tests/IDL_Test
-//
-// = FILENAME
-//    README
-//
-// = AUTHOR
-//    Jeff Parsons <j.parsons@vanderbilt.edu>
-//
-// ============================================================================
+$Id$
 
 This test is a collection of IDL files that once caused IDL compiler
 or C++ compiler errors, plus a dummy main.cpp for the build. There is
@@ -27,7 +14,7 @@ are uncovered and fixed, new examples will be added to the suite, to
 ensure that the bugs do not recur.
 
 The -GA option has been added to the IDL compiler command line. This
-option generates the implementations of type codes and Any 
+option generates the implementations of type codes and Any
 insertion/extraction operators in a separate file with the
 extension *A.cpp. These files have been added to the build, to make
 sure that the option functions correctly for all the IDL types
@@ -48,7 +35,7 @@ that will then be compiled by the C++ compiler on your platform.
 
 To run the test, type 'main' at the command line. The generation of
 correct IOR prefixes in pragma.idl is checked in the body of main().
-The rest of the .idl files need only to build cleanly. To test the 
-client/server functionality of the various IDL types and operations, 
+The rest of the .idl files need only to build cleanly. To test the
+client/server functionality of the various IDL types and operations,
 see the test suite in ACE_wrappers/TAO/tests/Param_Test.
 
diff --git a/TAO/tests/Objref_Sequence_Test/README b/TAO/tests/Objref_Sequence_Test/README
index bae3893870e..58ed81f41de 100644
--- a/TAO/tests/Objref_Sequence_Test/README
+++ b/TAO/tests/Objref_Sequence_Test/README
@@ -1,22 +1,24 @@
 /**
 
+$Id$
+
 @page Large Object Reference Sequence Test README File
       This test is for testing large Sequences of Object
       references. The test was donated by Petr Tuma
       <petr.tuma@mff.cuni.cz> with the necessary TAO'ification by Bala.
       This test failed in TAO 1.2 and 1.2.1.
-      
+
       Run the test as follows
 
 $ ./server -o file.ior
 $ ./client -k file://file.ior
 
       The test takes a long time to complete. Please do not include it
-      in the daily builds. 
+      in the daily builds.
 
 $ ./run_test.pl
 
-	the script returns 0 if the test was successful. 
+	the script returns 0 if the test was successful.
 
 
 */
diff --git a/TAO/tests/QtTests/README b/TAO/tests/QtTests/README
index 29393ece1f1..4689ee85656 100644
--- a/TAO/tests/QtTests/README
+++ b/TAO/tests/QtTests/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Introduction:
 
@@ -8,7 +8,7 @@ creates a dialog with a quit button & a slider. On dragging the slider
 the display on the server dialog box will change. On pressing the Quit
 button the ORB would be shutdown and the movement of the slider will
 NOT be communicated to the server. The user can kill the windows to
-exit. 
+exit.
 
 To run the server and the client simply do the following:
 
diff --git a/TAO/tests/RTCORBA/Collocation/README b/TAO/tests/RTCORBA/Collocation/README
index ddf7fbe3ce4..99ea2f32275 100644
--- a/TAO/tests/RTCORBA/Collocation/README
+++ b/TAO/tests/RTCORBA/Collocation/README
@@ -9,7 +9,7 @@ There are multiple servants in this test:
   thread pool.
 
 - One servant is in a POA with the CLIENT_PROPAGATED policy and is
-  serviced by a thread pool without lanes.  
+  serviced by a thread pool without lanes.
 
 - Two servants are in a POA with the SERVER_DECLARED policy and is
   serviced by a thread pool without lanes.  One of the servant is at
diff --git a/TAO/tests/RTCORBA/Diffserv/README b/TAO/tests/RTCORBA/Diffserv/README
index f1a80b25b34..245664fbf74 100644
--- a/TAO/tests/RTCORBA/Diffserv/README
+++ b/TAO/tests/RTCORBA/Diffserv/README
@@ -24,7 +24,7 @@ policy. This ensures that all replies sent from the POA have the dscp
 set. It registers a servant with this POA. Client obtains the object
 reference. Client then performs several invocations on the object.
 
-To run (on Unix): 
+To run (on Unix):
 -----------------
 
 $ ./server -ORBdebuglevel 1 -p 20000
diff --git a/TAO/tests/RTCORBA/Explicit_Binding/README b/TAO/tests/RTCORBA/Explicit_Binding/README
index d3f8558d143..95f3e0ea492 100644
--- a/TAO/tests/RTCORBA/Explicit_Binding/README
+++ b/TAO/tests/RTCORBA/Explicit_Binding/README
@@ -3,8 +3,8 @@ $Id$
 This is a test for <Object::_validate_connection> method, i.e.,
 explicit binding functionality.
 
-Description.  
--------- 
+Description.
+--------
 The goal of this test is to check that <validate_connection>
 establishes connections appropriate for the effective policy
 overrides, and that it detects policy misconfigurations and reports
diff --git a/TAO/tests/RTCORBA/Linear_Priority/README b/TAO/tests/RTCORBA/Linear_Priority/README
index 5064c84bdce..9fab4ff8822 100644
--- a/TAO/tests/RTCORBA/Linear_Priority/README
+++ b/TAO/tests/RTCORBA/Linear_Priority/README
@@ -31,6 +31,6 @@ ORBScopePolicy options in svc.conf file.
       NO          YES         YES          NO
       NO          NO          NO           YES
       YES         NO          NO           YES
-      YES         YES         NO           YES      
+      YES         YES         NO           YES
       NO          NO          YES          YES
       NO          YES         YES          YES
diff --git a/TAO/tests/RTCORBA/Priority_Inversion_With_Bands/README b/TAO/tests/RTCORBA/Priority_Inversion_With_Bands/README
index d49a4f22696..1a7df3eb88f 100644
--- a/TAO/tests/RTCORBA/Priority_Inversion_With_Bands/README
+++ b/TAO/tests/RTCORBA/Priority_Inversion_With_Bands/README
@@ -1,4 +1,3 @@
-
 $Id$
 
 Description:
@@ -35,7 +34,7 @@ different connections.
 (c) shows priority inversion as low priority requests get processed
 before high priority requests.  This is because only one connection is
 used for both low and high priority requests.  Therefore, the high
-priority requests are queued behind the low priority requests. 
+priority requests are queued behind the low priority requests.
 
 (d) shows improvement on (c) since using bands allows the high
 priority requests to go on a different connection than the low
diff --git a/TAO/tests/RTCORBA/Server_Declared/README b/TAO/tests/RTCORBA/Server_Declared/README
index 43152bf757a..c83a1e6e83f 100644
--- a/TAO/tests/RTCORBA/Server_Declared/README
+++ b/TAO/tests/RTCORBA/Server_Declared/README
@@ -8,7 +8,7 @@ Scenario:
 The server creates a POA with RTCORBA::SERVER_DECLARED priority model
 policy.  Two objects are created using this POA, one inherits the POA
 priority and the second one overrides POA priority with its own.
-Server threadpool resources are configured appropriately.  
+Server threadpool resources are configured appropriately.
 
 The client obtains two object references and invokes a method on each
 several times.  On each invocation, the client passes object's server
diff --git a/TAO/tests/Smart_Proxies/Policy/README b/TAO/tests/Smart_Proxies/Policy/README
index f24653ec589..bda209b8df8 100644
--- a/TAO/tests/Smart_Proxies/Policy/README
+++ b/TAO/tests/Smart_Proxies/Policy/README
@@ -26,11 +26,11 @@ be provided by the user and must derive from the generated
 TAO_Default_Proxy_Factory class.
 
 This test particularly is used to test out the different policies for the
-smart proxy.  If the same smart proxy is needed for the interface the 
+smart proxy.  If the same smart proxy is needed for the interface the
 "one-shot" policy is to be used by which once a smart proxy factory is
 registered it is retained until the program terminates.  This is the default
 behavior.  But if a more flexible option is desired where the smart proxy
-can be different with every instance of the target object, then the 
+can be different with every instance of the target object, then the
 one-shot plolicy has to be disabled by passing a 0 at creation time.
 
 For execution of the test:
@@ -39,7 +39,7 @@ For execution of the test:
 
 2) ./server -o test2.ior
 
-2) ./client 
+2) ./client
 
 The -f0 option tries out the "per-object" policy and the -f1 (default)
 tries out the "one-shot" aka "per-interface" policy.
diff --git a/TAO/tests/Smart_Proxies/dtor/README b/TAO/tests/Smart_Proxies/dtor/README
index 9124b5aebf4..7f057fb2a05 100644
--- a/TAO/tests/Smart_Proxies/dtor/README
+++ b/TAO/tests/Smart_Proxies/dtor/README
@@ -1,8 +1,8 @@
 $Id$
 
-This test is to test if the destruction process 
-and the _non_existent() function in the smart proxy 
-is working properly. 
+This test is to test if the destruction process
+and the _non_existent() function in the smart proxy
+is working properly.
 
 For execution of the test:
 
diff --git a/TAO/tests/UNKNOWN_Exception/README b/TAO/tests/UNKNOWN_Exception/README
index ee867ed21f7..abbeda80b6b 100644
--- a/TAO/tests/UNKNOWN_Exception/README
+++ b/TAO/tests/UNKNOWN_Exception/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Description:
 
@@ -13,7 +13,7 @@ the UNKNOWN exceptions.
 
 Expected output:
 
-A successful run is one without any asserts.  
+A successful run is one without any asserts.
 
 The server should say: