Database Reference
In-Depth Information
<wlevs:event-type-repository>
<wlevs:event-type type-name=" cargoBooking ">
<wlevs:properties>
<wlevs:property name=" cargoID "
type=" long" />
<wlevs:property name=" bookingTime
" type="timestamp" />
</wlevs:properties>
</wlevs:event-type>
</wlevs:event-type-repository>
<adapter>
<record-parameters>
<dataset-name>bookingRecPlay</dataset-name>
<event-type-list><event-type>
cargoBooking </event-type></event-type-list>
</adapter>
In this case, it's a cargoBooking event, and this event could be one of the
many defined events in the event type repository at the beginning of the configur-
ation file. Actually, the <event-type-list> part is optional in adapter de-
claration, and if the event type list is omitted, all types of events will be recorded
for further playback.
3. And now the playback itself. It's configured in the <playback-parameters>
group and is actually pretty similar to <record-parameters> ; here again,
we can use various components for playback events. In the following code, we
are adding the playback functionality to the stream, and it must be the down-
stream node from the recording component (which is absolutely logical):
<stream>
<name>cargoBookingStream</name>
<playback-parameters>
<dataset-name> bookingRecPlay
</dataset-name>
<event-type-list>
<event-type>
cargoBooking </event-type>
</event-type-list>
<provider-name> event-rdbms-provider
</provider-name>
Search WWH ::




Custom Search