Message Manager

(In theory, at least)

The nightly build of SMM now has all Sonic-specific logic separated from the main program. The main program compiles without any references to SonicMQ libraries and this opens the door to implementing support for other MQs.

All sonic-specific code is to be found in the “sonic-src” directory of the mercurial repository, all core code is in “src”. There probably still are some Sonic-specific assumptions in there, we’ll have to work those out when we get to them.

If anyone is interested in implementing support for another MQ, please contact me before writing any code so I can explain the process and structure of the application to you. I will document this in time, but not right now.

I have received some reports of trouble running the Sonic 6.1 version of Sonic Message Manager on Java 1.6.0_15. Because of this, I have changed the platform requirements for that specific version of SMM to Java 1.5.x – 1.6.14.

If you only have Java 1.6.0_15 or higher installed, java web start will attempt to install a compatible JRE for you if you want to run the Sonic 6.1 version of SMM. If you are using any other version of Sonic, any Java 1.5 or higher JVM will work just fine.

This is a temporary measure until I find out what Sun has changed in j2se 1.6.0_15 and what I need to do to work around it (if at all possible).

If you are running Sonic Message Manager with Java version 1.6.0_10 or later, the update policy for Sonic Message Manager has been changed.

Java Web Start will now check for updates in the background, while starting the application. When an update has been found, you will be informed of this the next time you start the application and you will have the option to install it.

This improves startup times because the update check is no longer done before starting the app. It should also dramatically improve startup time when you are not connected to the internet.