This is the mapping for an IDL structure which specifies
an initializer for a value type. A value can contain all the
elements that an interface can as well as the definition of
state members, and initializers for that state. In order to
ensure portability of value implementations, designers may
also define the signatures of initializers (or constructors) for
non abstract value types. Syntactically these look like local
operations except that they use the keyword init for the "name" of
the operation, have no return type, and must use only in parameters.
There may be any number of init declarations, as long as the signatures
of all the initializers declared within the same scope are unique.
Using the same signature as one found in a less-derived type is allowed.
The mapping of initializers is language specific and may not always
result in a one to one correspondence between initializer signatures
and the programming language constructs into which they map. This is
because the mapping from IDL types into programming language types is
not isomorphic; several different IDL types may map to the same
programming language type. Hence defining initializers with the same
number of parameters with types that are "similar" (e.g. char and wchar,
signed and unsigned integers, etc.) should be done with care. Value types
may also be abstract. They are called abstract because an abstract value
type may not be instantiated. No or may
be specified. However, local operations may be specified.
Essentially they are a bundle of operation signatures with a purely
local implementation. Note that a concrete value type with an
empty state is not an abstract value type.
The following shows an example of defining a value type with an
initializer.
Example:
valuetype EmployeeRecord {
private string name;
private string email;
private string SSN;
init(in string name, in string SSN);
};
Value types do not map to org.omg.CORBA.Object's.
For further API reference and developer documentation, see . That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Java, Java 2D, and JDBC are trademarks or registered trademarks of Sun Microsystems, Inc. in the US and other countries. Copyright 1993-2001 Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, California, 94303, U.S.A. All Rights Reserved.
