- All Implemented Interfaces:
- IDLEntity, Serializable
- public final class TaggedComponent
- extends Object
- implements IDLEntity
TaggedComponents contained in
TAG_MULTIPLE_COMPONENTS profiles are identified by
unique numeric tags using a namespace distinct form that is used for
profile tags. Component tags are assigned by the OMG.
Specifications of components must include the following information:
Specification of protocols must describe how the components affect
the protocol. The following should be specified in any protocol
definition for each
- Component ID: The compound tag that is obtained
- Structure and encoding: The syntax of the component
data and the encoding rules. If the component value is
encoded as a CDR encapsulation, the IDL type that is
encapsulated and the GIOP version which is used for encoding
the value, if different than GIOP 1.0, must be specified as
part of the component definition.
- Semantics: How the component data is intended to be
- Protocols: The protocol for which the component is
defined, and whether it is intended that the component be
usable by other protocols.
- At most once: whether more than one instance of this
component can be included in a profile.
TaggedComponent that the protocol uses:
- Mandatory presence: Whether inclusion of the component
in profiles supporting the protocol is required (MANDATORY
PRESENCE) or not required (OPTIONAL PRESENCE).
- Droppable: For optional presence component, whether
component, if present, must be retained or may be dropped.
The component data associated with the component id.
The tag, represented as a component id.
|Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
public int tag
- The tag, represented as a component id.
public byte component_data
- The component data associated with the component id.
public TaggedComponent(int _tag,
Submit a bug or feature
For further API reference and developer documentation, see Java 2 SDK SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 2003, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.