| 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 10.0 R4 to SAM 10.0 R5
- EventVessel - Class attributes for some or all classes may not appear depending on the <resultFilter-Set> defined upon registration. Only attributes within an AttributeValueChangeEvent, ObjectCreationEvent, or ObjectDeletionEvent for an AlarmInfo object may be suppressed from the EventVessel when a
is defined. If no attributes within an AttributeValueChangeEvent, ObjectCreationEvent, or ObjectDeletionEvent for an AlarmInfo object match the , then the entire event is suppressed and does not appear in the EventVessel. - XMLFilterChangeEvent - The message may contain <resultFilter-Set> data if specified in the registerNotification command.
- XMLFilterChangeEvent - The event is sent on the 5620-SAM-topic-xml-fault topic and the 5620-SAM-topic-xml-filtered topic when a subscribed user's OSS Alarm Filter changes. The message contains the <alarmFilter> being used for the client.
- alarmStatusChangeEvent - The JMS header properties <eventName> and <ALA_eventName> for this event have been changed from 'AttributeValueChange' to 'AlarmStatusChange'.
- 5620-SAM-topic-xml-fault - alarmStatusChangeEvent JMS events are no longer sent on this topic.
Release SAM 9.0 R8 to SAM 10.0 R1
- XMLFilterChangeEvent - The event is sent on the 5620-SAM-topic-xml-filtered topic after a client is deregistered for event notification. The message has no filter defined for the deregistered client.
None.