Examples of buri.ddmsence.ddms.IDDMSComponent

buri.ddmsence.ddms.IDDMSComponent

Interface for a single DDMS element.

All DDMS components should be valid after instantiation and can output themselves in various formats. Implementation classes are divided up into packages based on the five Core sets: Metacard Info, Security, Resource, Summary Content, and Format.

Accessors which return string-based data will always favour an empty string over a null value.

In general, Java classes are implemented for:

Elements which are explicitly declared as DDMS Categories in the DDMS documentation are always implemented (ddms:identifier).
Elements which merely enclose important data AND which have no special attributes are never implemented (ddms:Media).
Data which can be represented as a simple Java type AND which has no special attributes is represented as a simple Java type (ddms:email).
Attributes are generally implemented as properties on an Object. The exceptions to this are the ISM, SRS, and XLink AttributeGroup, which decorates many DDMS components.

@author Brian Uri! @since 0.9.b

   * 
   * @param theClass the class of the component to build
   * @return a valid component
   */
  private IDDMSComponent inputLoop(Class<?> theClass) throws IOException {
    IDDMSComponent component = null;
    while (component == null) {
      try {
        component = CONSTRUCTOR_BUILDERS.get(theClass).build();
      }
      catch (Exception e) {

    public MetacardInfo commit() throws InvalidDDMSException {
      if (isEmpty())
        return (null);
      List<IDDMSComponent> childComponents = new ArrayList<IDDMSComponent>();
      for (IBuilder builder : getChildBuilders()) {
        IDDMSComponent component = builder.commit();
        if (component != null) {
          childComponents.add(component);
        }
      }
      return (new MetacardInfo(childComponents, getSecurityAttributes().commit()));

Examples of buri.ddmsence.ddms.IDDMSComponent

Related Classes of buri.ddmsence.ddms.IDDMSComponent