Guidelines and Restrictions

The following guidelines and restrictions should be followed in order to enable platform interoperability:

The full class name (including package\namespace) in all platforms should be identical.

Note

Since java packages use a different naming convention than .NET namespaces, it is recommended to use the SpaceClass(AliasName="") feature to map a .NET class to the respective java class.

The properties/fields stored in the space in all platforms should be identical.

In Java, only properties are serialized into the space. In .NET, both fields and properties are serialized, so you can mix and match them.

Since java properties start with a lowercase letter, whereas .NET properties usually start with an uppercase letter, it is recommended to use the SpaceProperty(AliasName="") feature to map a property/field name from .NET to java.

Only the types listed in the table below are supported. If one of your fields uses a different type, you can use the class only in a homogeneous environment.

Arrays of these types are supported as well.
You can also use .NET enumerations, which are treated as their underlying .NET type. Java enums are not supported.
If your class contains a field whose type is not in the table, you can use SpaceExclude to exclude it from the space.
Some of the types have different characteristics in .NET and Java (signed\unsigned, nullable\not nullable, precision, etc.) This can lead to runtime exceptions (e.g. trying to store null in a .NET structure) or unexpected results (e.g. copying values between signed and unsigned fields).

Supported Types for Matching and Interoperability

The following types are supported by the space for matching and interoperability:

These types can be either nullable or not nullable in .NET, whereas in java they are always nullable.

In .NET a DateTime is measured in ticks (=100 nanoseconds) since 1/1/0001, whereas in java a Date is a measured in milliseconds since 1/1/1970.

The types Decimal (.NET) and BigDecimal (java) have different precision and range (see .NET and java documentation for more details). In addition, be aware that serialization/de serialization of these types is relatively slow, compared to other numeric types. As a rule of thumb these types should not be used, unless the other numeric types precision/range is not satisfactory.

Important

Java 8’s LocalDate, LocalTime, LocalDateTime are currently not interoperable with the .NET DateTime class.