Package com.priint.pubserver.comet.entity.statement

Enum Class Statement.StatementDescriptor

java.lang.Object
java.lang.Enum<Statement.StatementDescriptor>
com.priint.pubserver.comet.entity.statement.Statement.StatementDescriptor
All Implemented Interfaces:
Serializable, Comparable<Statement.StatementDescriptor>, Constable
Enclosing class:
Statement
public static enum Statement.StatementDescriptor extends Enum<Statement.StatementDescriptor>
The StatementDescriptor enumeration classifies several types of statements:
  • ACTIONS (speaking in comet3 terms): the script id denotes the type of this statement, e.g. a frame rule or a product panel script. Usually the script id is mapped to the classId when transforming comet statements to comet3 actions, though there are special cases (e.g. repeating elements) when the script id has to be mapped to the type field
    Actions have the statement type StatementType.ACTION
  • PANELSTATEMENTS: the script id denotes the id of this statement, e.g.: 55 for the top level product hierarchy.
    Panel statements have the statement type StatementType.PANELSTATEMENT, also most panel statements have a default statement, which can be used in most environments.
    Some panel statements may require adaption for certain project environment (such as login script, document event scripts etc.), these are copied to configuration files, which can be edited by the user.
    The script id is mapped to the panel statements id field when transforming comet statements to comet3 panel statements, thus each panel statement is unique
  • DEFAULTACTIONS: these scripts are generated for new comet projects or updated in existing projects according to the UpdatePolicy defined for this script.
  • other types (e.g. conditions): the script id has no meaning for these types. They are tagged with statement types according to their purpose, e.g. StatementType.CONDITION for condition statements.
CAUTION This enumeration includes values for all comet3 statement types, even though are unused, not supported any more or not required in a SOAP / PublishingServer environment.
Watch for the @Obsolete annotation, this will also give you a hint, why this particular statement should not be used.