it seems the net.sf.zekr.engine.theme.TemplateEngine constructor catches the
exception,
Error using VM library : VM_global_library.vm
meaning that context is never initialised. but since the exceptions been handled by catch zekr carries on. better to initialise context no matter what here? this is a
slightly better hacky fix than previously
it seems the net.sf. zekr.engine. theme.TemplateE ngine constructor catches the library. vm
exception,
Error using VM library : VM_global_
meaning that context is never initialised. but since the exceptions been handled by catch zekr carries on. better to initialise context no matter what here? this is a
slightly better hacky fix than previously
diff -ruN net/sf/ zekr/engine/ template/ TemplateEngine. java net.new/ sf/zekr/ engine/ template/ TemplateEngine. java zekr/engine/ template/ TemplateEngine. java 2008-06-26 19:15:32.000000000 +0100 sf/zekr/ engine/ template/ TemplateEngine. java 2010-01-14 01:30:48.022705986 +0000
System. setProperty( "zekr.home" , Naming. getWorkspace( ));^M
Velocity. setExtendedProp erties( new ExtendedPropert ies("res/ config/ lib/velocity. properties" ));^M
Velocity. init(); ^M ();^M
Logger. getLogger( this.getClass( )).log( e);^M ();^M
--- net/sf/
+++ net.new/
@@ -41,10 +41,10 @@
- context = new VelocityContext
} catch (Exception e) {^M
}^M
+ context = new VelocityContext
}^M
^M
/**^M