Versions Compared

Version Old Version 6 New Version 7
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Flyway is now used to maintain the database schema of the user preferences database. To initialise the Flyway schema on an existing user preferences database, it is necessary to update the schema to the latest non-Flyway version and run MyTimetable once with the setting userPrefs.flyway.initOnMigrate set to true. Please ask our support department for further information.
  • The version numbering policy of MyTimetable has changed. The version number now consists of: <major version>.<minor version>.<git short commit hash>, and can be found in the Settings dialog, under 'Status'.
  • Spring profiles are now used to select the authentication method. Due to this change, it may be necessarto necessary to update the spring.profiles.active environment variable if it exists in your configuration.
  • Infinispan is now used as cache provider for Spring-based method caching. This caching is used to improve performance of the internal user preferences and subscription services.
  • UTF-8 is now fully supported by MyTimetable. In case you encounter any issues with character encoding, please contact us to resolve these issues.
  • Log spamming has been fixed: iCalender feeds with incorrect authentication or users that are required to login do not cause excessive log messages anymore.
  • Several memory and class loader leaks have been fixed, by upgrading c3p0 and JTDS (the database driver and connection pool), and the connection pool settings have been tuned based on experience from several large MyTimetable instances.
  • AspectJ (1.7.2) is now a fundamental part of MyTimetable. As such it is possible to alter or override certain MyTimetable functionality for certain customers using aspect-oriented programming.
  • Several Syllabus Plus SQL connection performance improvements have been made by using read-only transactions, optimising DAO's and using the SQL2005 Hibernate dialect. Due to the latter change, SQL Server 2005 or higher is now required for MyTimetable (but it always has been for the Scientia Scheduled Extract, so this change should not cause issues for anyone).
  • JSP pages have been updated to only include JSTL and any inline code has been removed.
  • Upgrades of dependencies:
    • Servlet API (2.5)
    • Spring (3.2.1.RELEASE)
    • CXF (2.7.2)
    • Spring Security (3.1.3.RELEASE)
    • Spring Security SAML (1.0.0-20121118)
    • Spring Security Oauth2 (1.0.0.RELEASE)
    • Spring Mobile (1.0.1.RELEASE)
    • Jackson (1.9.11)
    • JTDS (1.2.7)
    • Ehcache (2.6.2)
    • Joda time (2.1)
    • Gradle (1.3)
    • iCal4j (1.0.4)
    • require.js, moment.js and dependencies

...