[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Assembly: Db4objects.Db4o (in Db4objects.Db4o.dll)
advises db4o to try instantiating objects with/without calling
constructors.
Namespace: Db4objects.Db4o.Config
Assembly: Db4objects.Db4o (in Db4objects.Db4o.dll)
Syntax
Visual Basic (Declaration) |
---|
Sub CallConstructors ( _ flag As Boolean _ ) |
C# |
---|
void CallConstructors ( bool flag ) |
Visual C++ |
---|
void CallConstructors ( bool flag ) |
Parameters
- flag
- System.Boolean
- specify true, to request calling constructors, specify false to request not calling constructors.
Remarks
advises db4o to try instantiating objects with/without calling
constructors.
Not all JDKs / .NET-environments support this feature. db4o will attempt, to follow the setting as good as the enviroment supports. In doing so, it may call implementation-specific features like sun.reflect.ReflectionFactory#newConstructorForSerialization on the Sun Java 1.4.x/5 VM (not available on other VMs) and FormatterServices.GetUninitializedObject() on the .NET framework (not available on CompactFramework). This setting may also be overridden for individual classes in Db4objects.Db4o.Config.IObjectClass.CallConstructor .
The default setting depends on the features supported by your current environment.
Not all JDKs / .NET-environments support this feature. db4o will attempt, to follow the setting as good as the enviroment supports. In doing so, it may call implementation-specific features like sun.reflect.ReflectionFactory#newConstructorForSerialization on the Sun Java 1.4.x/5 VM (not available on other VMs) and FormatterServices.GetUninitializedObject() on the .NET framework (not available on CompactFramework). This setting may also be overridden for individual classes in Db4objects.Db4o.Config.IObjectClass.CallConstructor .
The default setting depends on the features supported by your current environment.