public interface ExtrinsicObject extends RegistryEntry {
// Public Instance Methods
public abstract String getMimeType( )
throws javax.xml.registry.JAXRException; //L1
public abstract javax.activation.DataHandler getRepositoryItem( )
throws javax.xml.registry.JAXRException; //L1
public abstract boolean isOpaque( )
throws javax.xml.registry.JAXRException; //L1
public abstract void setMimeType(String mimeType)
throws javax.xml.registry.JAXRException; //L1
public abstract void setOpaque(boolean isOpaque)
throws javax.xml.registry.JAXRException; //L1
public abstract void setRepositoryItem(javax.activation.DataHandler repositoryItem)
throws javax.xml.registry.JAXRException; //L1
}
Most of the interfaces in the
javax.xml.registry.infomodel package represent
data that is held within the registry itself and is of a type that
the registry understands. This is not the case for an
ExtrinsicObject. The
ExtrinsicObject interface represents information
that does not have any meaning to and is not interpreted by the
registry, which treats it simply as data and stores it in an
associated repository from which it can be retrieved on demand. To
add an ExtrinsicObject to the registry, use the
LifeCycleManager createExtrinsicObject(
) method, which requires a DataHandler
that can be used to retrieve the data to be written to the repository
as a byte stream. Once a ExtrinsicObject is
created, you can use the getRepositoryItem( )
method to get a DataHandler that retrieves its
content from the repository and the getMimeType( )
method to get the MIME type of the data. The setOpaque(
) method can be used to mark the data as opaque, so that
the registry should not attempt to interpret it in any way. This
might be done if the data is encrypted before being submitted to the
registry.
Since ExtrinsicObjects require storage outside the
registry, they represent a level 1 feature.
