| 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 6.0 to SAM 7.0
- IncrementalRequestEvent - This event is generated for activity related to generic.GenericObject.triggerIncrementalRequest().
See generic.IncrementalContext() for a list of applications that create these messages.
- Jar changes - Support for Java 5 is deprecated. SAM-O jars (samOssJBoss.jar, samOss.jar or samOssNoJms.jar) are created with Java 5.
The main server and JMS server use Java 6.
Clients must use the SAM-O jar that corresponds to the same SAM or CPAM release.- Alarm debouncing: During alarm storms, duplicate alarm events are suppressed.
- Connection exceptions: JMS authentication failures now indicate when the server is not fully started to differentiate between credential failures and server initialization.