Package wt.eff.form

This package consists primarily of EffForm interfaces - each recodesenting a particular form (aka type) of effectivity and each intended to be implemented by concrete wt.eff.EffRecord implementations.

See:
Description

Interface Summary

BlockEffForm	An EffForm representing block effectivity statements.
DateEffForm	An EffForm representing date effectivity statements.
EffForm	An EffForm represents a particular form (aka type) of effectivity and is intended to be implemented by concrete EffRecord implementations.
LotEffForm	An EffForm representing lot number effectivity statements.
MSNEffForm	An EffForm representing manufacturing sequence number effectivity statements.
SerialEffForm	An EffForm representing serial number effectivity statements.
UnitEffForm	An EffForm representing unit effectivity statements.

Class Summary

EffFormHelper

Helper class for this package containing utility routines.

Package wt.eff.form Description

This package consists primarily of EffForm interfaces - each recodesenting a particular form (aka type) of effectivity and each intended to be implemented by concrete wt.eff.EffRecord implementations. The right EffForm interface for a particular EffRecord implementation depends on the contract an EffRecord implementation supports. For example: wt.eff.PendingSerialNumberEffectivity is an effectivity record implementation to support Serial Eff Forms (that are still pending - seeking approval / release of a change notice). Hence it implements SerialEffForm interface to enforce that contract.

In general, EffForm and its sub-interfaces, are used to classify the various effectivity forms supported . Apart from that, associations to wt.eff.EffContext and wt.eff.EffRange are generalized and specified at an EffForm level, supporting the notion, that an EffForm itself knows for the most part what are the expected associations to these classes. In other words, it knows what kind of range and what kind of association to EffContext is expected for its purposes. Concrete wt.eff.EffRecord implementations do have a chance to override these associations if need be.