[openorb-commits] CVS: OpenORB/src/config default.xml,1.27,1.28

[<lk...@us...>]

Update of /cvsroot/openorb/OpenORB/src/config
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4887/src/config

Modified Files:
	default.xml 
Log Message:
removed property iiop.useNativeLibrary in favour of iiop.deserializationEngine
Allow lazy initialization of DeserializationKernel and make lazy:auto the default behaviour
On Sun JDK 1.5 test errors are down to one error in PrimitiveTest.testValuetypes() because of lazy initialization

Index: default.xml
===================================================================
RCS file: /cvsroot/openorb/OpenORB/src/config/default.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- default.xml	22 Jul 2004 09:49:45 -0000	1.27
+++ default.xml	14 Nov 2004 21:38:35 -0000	1.28
@@ -655,7 +655,7 @@
 
     <!--
       NOTE: This feature has now been superseded by the stream decoration framework!
-    
+
       The following properties are helpful for tracing IIOP communication on the socket layer.
       Tools as Ethereal are not suitable when it comes to threading issues, i.e. finding bugs
       in badly synchronized code where different threads write to the same socket.
@@ -686,14 +686,36 @@
       </description>
     </property>
     -->
-    
-    <property name="useNativeLibrary" value="false">
+
+    <property name="deserializationEngine" value="lazy:auto">
       <description>
-      This property circumvents the automatic detection of the VM vendor and the
-      VM dependant marshaling engines by using a native library for the
-      RMI-IIOP and Java Valuetype unmarshaling.
-      Default is false.
-      The native library can be found in the native CVS module.
+      This property allows configuration of the deserialization engine to
+      use for RMI-IIOP and Java Serializable unmarshaling.
+
+      Possible values:
+
+      -   'auto': use automatic detection of the VM vendor and create a
+        VM dependent marshaling engine. For a list of supported VMs
+        please see the JavaDoc of the DeserializationKernelFactory class.
+
+      -   'native': use a native library and JNI. This works with any VM but
+        requires native code plus special setup of the VM environment in your
+        operating system. The native library can be found in the native CVS module,
+        including precompiled binaries for some platforms.
+
+      -   'none': no support for RMI-IIOP, even if your VM supports it. Use this
+        option to make sure that your software does not use any ORB features that
+        depend on the VM.
+
+      A prefix of 'lazy:' avoids creation at ORB startup time and defers creation of the
+      deserialization engine until it is first used.
+
+      Using 'lazy:' is not recommended if you need to achieve fail-fast behaviour.
+      Using the 'lazy:' prefix is recommended if you are not sending Serializables
+      over the wire - your application will work even if your VM is not supported
+      for 'auto' or the operating system is not set up correctly for 'native'.
+
+      Default value for deserializationEngine is 'lazy:auto'.
       </description>
     </property>
 
@@ -705,10 +727,10 @@
       interface.
       If this set is empty then the set defaults to the entries stated below.
       </description>
-      
+
       <!-- Handles boostReceivePriority functionality -->
       <property name="1" value="org.openorb.orb.net.PriorityBoostingSocketStreamDecorationStrategy$Factory" />
-      
+
       <!-- Handles bufferedInputStreamSize and bufferedOutputStreamSize functionality -->
       <property name="2" value="org.openorb.orb.net.BufferingSocketStreamDecorationStrategy$Factory" />