Additional SOA Patterns –Supporting Composition Controllers - Applied SOA Patterns on the Oracle Platform - page 555

• CodeName : This is the class name key reference that is identified using keys,
namely, PORT_CODE , VESSEL_CODE , and GARGO_ID .
• BusinessName : This is the business meaning of PORT_CODE , such as POD,
POL, Port of Destination, Port of Origin, and so on. You need it for your own
sake—the context of the message must be human readable.
• ParameterType : This is an optional, scalar (string, number, or byte), or com-
posite data/object (array, CSV list, or vector) type.
• Order : This is optional. As long as a parameterized event can be an array, vec-
tor, or sequence of basic types, this index will represent the position of an indi-
vidual element in the sequence.
Technically speaking, you can see the object context as a form of name-value pairs array
with some additions for historical retrospection; we discussed it earlier in Chapter 5 ,
Maintaining the Core - the Service Repository , while talking about Message Header.
Here, in the following figure, you can see the simplified version of this complex type that
is suitable for events propagation (or, more correctly, basic events' notifications). The fol-
lowing structure is essential in order to understand the event-type repository of Oracle
Event Processing: