Release Notes 1.4.4.1

From bemoko developer wiki

Jump to: navigation, search

Released on 12 November 2010

Summary

1.4.4.1 is a service pack to bemokoLive that builds on top of 1.4.4. It is recommended that all users upgrade to 1.4.4.1.

1.4.4.1 primarily brings operational improvements.

Enhancements

  • [LIVE-1330] - Support a plugin that does not escape XML on write to Freemarker template (@NoEscape)
  • [LIVE-1382] - Allow arbitrary hibernate properties to be set
  • [LIVE-1376] - Support file upload
  • [LIVE-1386] - Support lazy loading of GORM objects
  • [LIVE-1400] - Allow log4j configuration file location to be specified and initialise log4j in app start up if it is
  • [LIVE-1414] - Create email alert throttle, e.g. 50 errors per hour
  • [LIVE-1415] - Move Date field in email alert log into third line (behind version and build date) so that it always in a reliable location in the email alert
  • [LIVE-1416] - Do not log error for ClientAbortException, just do a warn - this is a client aborting the connection and so is not an exception
  • [LIVE-1418] - Allow the profile persistence to only be triggered for some requests
  • [LIVE-1419] - Upgrade ehcache to 2.3

Fixes

  • [LIVE-1348] - Exception in controller getView is ignored
  • [LIVE-1385] - Root plugins do not automatically escape content - they should
  • [LIVE-1394] - Text inputs in console cause parsing error when & include
  • [LIVE-1417] - Fix java.lang.ClassCastException: com.bemoko.live.platform.ui.SiteViewImpl cannot be cast to com.bemoko.live.platform.ui.SiteViewRenderer
  • [LIVE-1421] - Config files not being loaded from old location

Upgrade Notes

  • Config change : Hibernate property name to set database schema name is now aligned with the hibernate properties name, i.e. bemoko.datasource.hibernate.default_schema. In 1.4.4 it was bemoko.datasource.hibernate.schema, but this naming is no longer supported.
  • The intent property intent.type now returns the type of the intent, e.g. template, resource.

Setting the Location of the Log4j Configuration File

The log4j logging configuration file used by the bemoko application can now be specified independently from the default log4j spin-up. This is useful if you are deploying bemoko into an application server which has it's own log4j initialisation. To explicitly set the log4j file, set the bemoko.logging.log4j.file parameter on the JVM start up arguments, e.g. 

-Dbemoko.logging.log4j.file=/home/bemoko/config/log4j.xml

JBoss 5 Specific Build

A jboss5 specific version is available if you wish to get the enhanced logging support. Note the standard release runs find on JBoss5, albeit with the default JBoss logging instead of the enhanced bemoko logging.

Retrieved from "http://www.bemoko.com/wiki/Release_Notes_1.4.4.1"