Re: [Bodington-developers] i18n template compilation problem

[Alexis O'C. <ale...@co...>]

Alistair Young wrote:
> It seems that when you pre-compile the templates, it breaks i18n.
> 

Or even, i18n breaks template compilation.

> There are two ways round this:
> 
> 1) Don't pre-compile templates - bod can do it anyway
> 2) I change i18n to put resource files in the classpath so the full  
> path isn't required. That means the resource files will be separate  
> from the templates and we'll need a new WEB-INF/classes directory where  
> one didn't exist before.
> 
> anyone got any opinions?

Er, point (1) is quite true. However, your "contributions" are 
demonstrating very clearly why it is desirable to valaidate the 
templates prior to deployment(!). In addition to validation up until now 
  we've had pre-compilation too - i.e. generate all the templates and 
then you can even run Bodington on a JRE. Therefore, put the resource 
files on the CLASSPATH, and as you say, probably under 'WEB-INF/classes'.

Whilst we're on the subject, a slightly rhetorical question, but do you 
reckon the method XmlTemplate::compileI18NConfig(Element) will work on 
Windows!?!


Alexis