IdentifiantMot de passe
Loading...
Mot de passe oublié ?Je m'inscris ! (gratuit)
 
[Sommaire]  [Top 50]  [F.A.Q.]  [ Java SE ]  [ Java EE ]  [Javadoc standard]  [Contact]
[ 1.4.2 ]  [ 5.0 ]  [ 6.0
Rechercher   
Dans
Options   sensible à la casse
étendre la recherche aux descriptions
Préférences
fr en 
 
Moteurs de recherche
JavaTM 2 Platform Std. Ed. v1.4.2

org.omg.IOP
Class TaggedComponentHolder

java.lang.Object
  extended byorg.omg.IOP.TaggedComponentHolder
All Implemented Interfaces:
Streamable

public final class TaggedComponentHolder
extends Object
implements Streamable

TaggedComponents contained in TAG_INTERNET_IOP and 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:

  • Component ID: The compound tag that is obtained from OMG.
  • 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 used.
  • 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.
Specification of protocols must describe how the components affect the protocol. The following should be specified in any protocol definition for each 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.


Field Summary
 TaggedComponent value
           
 
Constructor Summary
TaggedComponentHolder()
           
TaggedComponentHolder(TaggedComponent initialValue)
           
 
Method Summary
 void _read(InputStream i)
          Reads data from istream and initalizes the value field of the Holder with the unmarshalled data.
 TypeCode _type()
          Retrieves the TypeCode object corresponding to the value in the value field of the Holder.
 void _write(OutputStream o)
          Marshals to ostream the value in the value field of the Holder.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

value

public TaggedComponent value
Constructor Detail

TaggedComponentHolder

public TaggedComponentHolder()

TaggedComponentHolder

public TaggedComponentHolder(TaggedComponent initialValue)
Method Detail

_read

public void _read(InputStream i)
Description copied from interface: Streamable
Reads data from istream and initalizes the value field of the Holder with the unmarshalled data.

Specified by:
_read in interface Streamable
Parameters:
i - the InputStream that represents the CDR data from the wire.

_write

public void _write(OutputStream o)
Description copied from interface: Streamable
Marshals to ostream the value in the value field of the Holder.

Specified by:
_write in interface Streamable
Parameters:
o - the CDR OutputStream

_type

public TypeCode _type()
Description copied from interface: Streamable
Retrieves the TypeCode object corresponding to the value in the value field of the Holder.

Specified by:
_type in interface Streamable
Returns:
the TypeCode object for the value held in the holder

Copyright 2003 Sun Microsystems, Inc. All rights reserved