| Overview | Package | Class | Deprecated |
The 5620 SAM-O JMS interface has evolved over several releases. This page identifies changes to the JMS interface. Changes are divided into two sections, event changes and interface changes. They are listed at a high level, detail of the change is defined in the developers guide. Please review the JmsTest class for examples on how to handle backwards compatibility for changes identified below.
Release SAM 9.0 R4 to SAM 9.0 R5
- EventVessel - New event sent on the 5620-SAM-topic-xml-filtered topic. This event contains a list of events in the message body that have been filtered for clients that use the registerNotification functionality. Message headers are not sent for the contained events.
- XMLFilterChangeEvent - New event sent on the 5620-SAM-topic-xml-filtered topic after client has successfully registered for event notification with a filter. It is used to notify clients that use the registerNotification functionality. The message includes the new filter that the client is registered for.
- ALA_isVessel appears in the message header to indicate whether the event is an EventVessel (true) or not (false).
- ALA_vesselSize appears in the message header for EventVessel events to indicate the number of contained events in the message body.
- 5620-SAM-topic-xml-filtered - New topic for filtering events. Only a basic subscription filter [ ALA_clientId in ('ossi@2', '') OR (MTOSI_objectType in ('KeepAliveEvent', 'StateChangeEvent', 'TerminateClientSession')) ] is required for this topic. All specific filtering is specified in a registerNotification command.
Events are filtered by the JMS publisher before they reach a client. It is up to the client to process the EventVessel to extract relevent data.