Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
jalarms-protobuf-1.6.0-javadoc.jar | 2011-10-11 | 69.7 kB | |
jalarms-protobuf-1.6.0-sources.jar | 2011-10-11 | 7.9 kB | |
jalarms-protobuf-1.6.0.jar | 2011-10-11 | 18.6 kB | |
README.txt | 2011-10-11 | 1.0 kB | |
jalarms-channels-1.6.0-sources.jar | 2011-10-11 | 13.6 kB | |
jalarms-channels-1.6.0.jar | 2011-10-11 | 24.0 kB | |
jalarms-aop-1.6.0.jar | 2011-10-11 | 3.2 kB | |
jalarms-channels-1.6.0-javadoc.jar | 2011-10-11 | 56.9 kB | |
jalarms-aop-1.6.0-javadoc.jar | 2011-10-11 | 26.3 kB | |
jalarms-aop-1.6.0-sources.jar | 2011-10-11 | 3.0 kB | |
jalarms-core-1.6.0-javadoc.jar | 2011-10-11 | 113.3 kB | |
jalarms-core-1.6.0-sources.jar | 2011-10-11 | 26.3 kB | |
jalarms-core-1.6.0.jar | 2011-10-11 | 33.2 kB | |
Totals: 13 Items | 396.8 kB | 0 |
jAlarms 1.6.0 BREAKING CHANGES AlarmSender is no longer a class; it is now an interface. The class is now called AlarmSenderImpl. If you are using IoC such as Spring or Guice to inject the AlarmSender into your components, then you only need to change the definition of the component to be AlarmSenderImpl, but you can leave the reference as AlarmSender. This change was made to accommodate new remote services: you can now setup an AlarmSender and publish it via RMI or connect to it using Protocol Buffers. You could even publish an AlarmSender in a JNDI node in a JEE container. There is a new module, jalarms-protobuf, which contains a server component to allow clients to connect remotely and send alarms via a single shared AlarmSender, as well as the client component that connects to the server component to send the alarms remotely. The client component implements the AlarmSender interface. The use of Protocol Buffers will also allow applications written in other languages to send alarms.