The follow procedure describe how you perform a reset on any definition
except for type definitions. For the procedure for type definitions, see Resetting
a type definition. Once the toolkit is running, to reset a definition, do
the following:
- To ensure that the toolkit uses the most recent definitions, determine
the order in which you reset the definitions by taking into account the following
items:
- When resetting a set of entities of the same type, reset the simple definitions
before resetting any composite definition that includes the simple definitions.
- When resetting a set of entities of different types, use the following
order:
- Settings
- Types
- Data
- Formats
- Contexts
- Processors
- When working with self-defined entities that have a split modularity,
reset only the required entity. If the modularity is mixed or grouped, reset
all the modified generic definitions before resetting the self-defined entity.
Note, however, that a modification in the definition of one hierarchy's context
does not have any effect if a context object instance already exists for this
definition. This is because the convertTagtoObject(Tag) method does not create
a new object instance in this case.
- Update the definition file with the new tag definition.
- Call the appropriate reset method. For example, to
reset a data entity called A, you would use the following method of the data
externalizer:
com.ibm.dse.base.DataElement.getExternalizer().reset("A");
- If the externalizer has a cache, clear it.