Component Custom Types

Create

When creating a new custom component type or a new version of a custom component type via the CLI create command, you set the following properties in the newtype.xml as specified in the component.xsd schema:

• Name

  The name of the custom component type

  Example: EAR

• DefaultDeploymentTargetType

  Name of the deployment target type that should be set by default when creating the component.

• Traceable

  If this property is set to false, no installation records are created for components based on the custom type.

  Possible values:

  • true
  • false

  Default: true

  Note: The default value for Components created in versions lower than 10 is true.

• baseType

  This parameters defines if the Component can be nested to another Component type (see: Working with Nested Components), if it is detached from another Component type (see: Working with Application Components) or if it is it bound to a certain Deployment Target type.

  Possible values:

  • Detached
  • TargetBound
  • Nested

• Properties

  The properties of component.

• DynamicProperties

  The dynamic properties of the component.

Notes:

• If you create a new component type version based on an existing type version, a clone of the old version will be created. You can therefore change any properties without affecting the older version.
• When updating a component custom type, changes to properties will immediately affect all current instances of that component type version. For example, if you delete a property, you will irreversible delete the data of all components (of that type version) which were entered for that property.
• For more information, see: Working with Custom Types
• Nested Components and general Components have the same default dynamic properties. For more information, see: Working with Nested Components

Delete

You cannot delete component types with instances.