Dwarf Server Framework 1.3.1

Upgrading

Content

• General upgrading guidelines
• Version 1.1 to 1.2.0
• Version 1.0.1 to 1.1
• Version 1.0 to 1.0.1

General upgrading guidelines

Create a fresh new installation by unpacking the distribution file and following the general installation instructions. Verify that the installation is working properly by running sample applications coming with the distribution. After that port your existing applications, configuration files and source code according to the following instructions:

Version 1.1 to 1.2.0

Installation:

• Dwarf Server Framework 1.3.1 now requires Java™ 2 version 1.4 or higher for the runtime operation and development. The initial setup does not require any additional Java extensions.

XML Configuration:

• move the key-store related attributes from SSLListener to TCPIPServer class, as well as the "protocol" attribute, which has been renamed to more suitable "SSLProtocol"
• change simple service names to the full service names in all entries with the subject-based policy permissions, which use the ServicePrincipal object
• use TCPIPServer instead of the MultiThreadServer as a container for simple TCP-based services

Development:

• all ThreadService and ThreadServer derivations must override the enableThread method to return true to enable the creation of a new thread
• use TCPIPServer instead of the MultiThreadServer as a base class for the custom TCP-based servers
• change all references to services' PRINCIPAL static field to the getPrincipal dynamic method
• the console commands derived from the Command abstract class must implement the abstract getDescription method instead of the previous getHelp method, and optionally may implement the printHelp method. The abstract execute method has two new arguments and implementations must reflect this change as well.
• remove all references to the addInstance method of the LogLevel class

Version 1.0.1 to 1.1

XML Configuration:

• use MultiThreadServer instead of the TCPServer (removed) as a container for simple TCP-based services
• use the subsystem identification strings for the trace attribute of the root configuration element instead of the previous "on" or "off" boolean values. Use empty string to completelly disable generating of the tracing messages.
• remove forceExit attribute from MainServer instances; it is not needed any more

Development:

• use MultiThreadServer instead of the TCPServer (removed) as a base class for the custom server classes
• replace IllegalParentException (removed) with the IllegalServiceClassException

Version 1.0 to 1.0.1

• MD5PasswordEncoder now encodes passwords using more suitable BASE64 encoding instead of the hexadecimal dump of byte array. If you were using custom password files you must convert the MD5 password digests back to byte arrays and then encode them again using BASE64 encoding. If you know the original passwords, you can use the PasswdCmd console command to encode the password strings manually.

Return to the main page.