Release Notes 1.4.5

From bemoko developer wiki

Jump to: navigation, search

Released on 6 January 2011

Summary

1.4.5 is the an update to bemokoLive that builds on top of 1.4.4.1.

Enhancements

[LIVE-1325] - Provide a way to load templates in ancestry other than parent
[LIVE-1378] - Improve space handling around in-line elements
[LIVE-1433] - Allow CSS to be overriden in the console
[LIVE-1440] - Enable the cache sizes to be set
[LIVE-1443] - Support execute and initialise with no arguments for plugins
[LIVE-1449] - Move ModuleController and PermissionException to core library (so that it's easier to add console functions)
[LIVE-1450] - Improve rendering of console on mobile
[LIVE-1461] - Support "lib" dependencies from site (as well as platform)

Fixes

[LIVE-1429] - Handle situation more elegantly where renderer plugin doesn't set input stream
[LIVE-1430] - Exception stack not cleaned up if exception thrown in interaction destroy phase
[LIVE-1436] - NPE when license directory is a file
[LIVE-1442] - admincontroller is executed before logincontroller
[LIVE-1444] - Profile access should be forced to true for console site
[LIVE-1446] - Config page in console throws exception when rendering integers
[LIVE-1447] - Site datasource JNDI lookup does not work if platform jndi datasource name starts with java:
[LIVE-1451] - Created in profile is not constrained to not null
[LIVE-1452] - org.hibernate.LazyInitializationException: could not initialize proxy - no Session when plugin reloads
[LIVE-1453] - Cache object browse template name has wrong capitalisation
[LIVE-1455] - Text from log error message is not reported in SMTP error alert
[LIVE-1457] - NPE when getting property in template from plugin when property does not exist
[LIVE-1458] - No such property exception when accessing property that does not exist from template

Documentation

Extending a template other than the parent

You have been able to extend a template from it's parent using

[#include template.parent]
<div>hello</div>

which effectively extends the content that would have been displayed with extra content (above or below). Now you can extend another template other than the direct parent, for example the template from the "320" ui

[#include template.getParent('320')]
<div>hello</div>

This gives you more control on how the template fallback flow works and makes it easier to override the default behaviour.

Including an extra jar in your site

You have already been able to define extra jars (libraries) that are required for the rendering of a site by adding lib dependencies to the site configuration, e.g.

<site>
  <lib>
    <jar module="htmlunit" group="net.sourceforge.htmlunit" version="2.5"/>  
    <jar module="custom" group="customgroup" version="1.0"/>  
    <jar module="commons-primitives" group="commons-primitives" version="1.0"/>      
  </lib>
</site>

previously this only looked for these jars in either the platform lib directory or dynamically downloaded using groovy's "grab". Now you can also include these jars in the lib directory of the site (or addon). bemoko now looks for the jar first in the site / addon lib directories, then in the platform lib directory and then tries to dynamically download it.

Simplification of execute and initialise method

Previously the initialise and execute methods needed to be defined with a Map argument which passes in the intent parameters, e.g.

def initialise(Map p) {
  ...
}
 
def execute(Map p) {
  ...
}

you no longer need to define this argument (although the system still supports the Map argument signature). You can now use the simpler version of these methods with no arguments:

def initialise() {
  ...
}
 
def execute() {
  ...
}

Customise the CSS of a console module

It is now possible to provide a CSS file to customise the look and feel of a particular console module. This can be done by creating a file called module.css in the console module UI directory, e.g. ui/root/console/mymodule/module.css.