Changelog: 9.1.16 - current

Release 9.1.20

1. bug-fix: After renaming a component the correct component will be selected now.
2. enhancement: API enhancement: The Content facade objects can now be used for template resources as well as content resources. The old constructors remain supported and default to content mode.
3. enhancement: Replaced the editor for date components with an improved calendar based one.

Release 9.1.19

1. bug-fix: Corrected the handling of createUser SQL statement in DBUserGroup.
2. bug-fix: Updated range of years in the date editor.
3. bug-fix: When running under the Java security manager, the retrieval of database connections now works more reliable when component manager methods are called by low-privileged packages.

Release 9.1.18

1. bug-fix: Added a workaround for a bug in the current Oracle 10 driver, which sometimes cut off a few bytes from the end of binaries during package import. This has no effect on users of other databases.
2. bug-fix: Using DBRoleGroup no longer throws an error when using the new init parameters.
3. enhancement: Added LastModifiedComponents action which delivers last modified components on the server.

Release 9.1.17

1. bug-fix: Updated client signature certificate.
2. bug-fix: Lock handling made stricter to prevent a bug where context changes would end up without shared locks. Private lock creation is now blocked if shared locks from different contexts would be involved.
3. bug-fix: Made the client ignore and log invalid type names (e.g. ones with double periods like "testpackage..testtype") instead of hanging on login.
4. enhancement: Added new optional initial parameters to DBRoleGroup and DBUserGroup to be more flexible. If you want to use these parameters, you have to add them in your project.xml configuration file.
5. bug-fix: Changed the behaviour of the "session expired" error mechanism. First, this means that specifying single pages (as opposed to folders) in public tags now works properly. Also, "component not found" errors (usually handled as HTTP error code 404) have priority over session expiry errors.
6. bug-fix: When using Java 6, the component name field in the "New Component" dialog did not have the focus by default, as it does when using Java 5. This has been changed, so that the field is now focused for both Java releases.