I see you point, and it just highlights the fact that .tml files are
allowed at the webapp root level which, itself, is an exception to the
rule. For components, the .tml and .properties file must be bundled
in the same package folder as the .class file.
For pages, and only pages, we allow the .tml to live in the webapp
root as a convienience for previewing. However, even that is
questionable, as a page that has an activation context will have a
different base URL than one that doesn't, meaning that relative URLs
to images and &etc. will always be somewhat tenuous (and Assets should
be used).
On Jan 30, 2008 2:01 PM, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
> On Jan 30, 2008 8:02 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>
> > Is your Contact.properties file in the correct place? It should be on
> > he classpath, with the .class file (not with the .tml file). Verify
> > this by putting ${site-label} into your template somewhere to see what
> > you get.
>
> May i piggy back this thread to ask if it sound resonable to have
> .properties files live side by side with .tml one?
> Since that files are usually manger by the same persons who manage the
> .tml, isnt't this the usual case?
>
> --
> Massimo
> http://meridio.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
