I don't think so. T5 is all about avoiding logic in the templates.

I would recommend creating a service that accesses those properties, if
you're copying the logic around.

On Wed, May 5, 2010 at 12:27 PM, Mark Allan <mark.al...@ed.ac.uk> wrote:

> Hi All,
>
> I've tried searching in vain for an answer to this, so have included my
> search terms throughout this email in case anyone is stuck on the same issue
> in the future - if it looks like I'm using various terms to refer to the
> same thing, that's why!
>
> I've got a T5 app which is almost ready to go live, so I've split it into
> two versions - service and development.  The service version runs under
> Tomcat and the development version runs under Jetty (via mvn jetty:run).
>
> Some URLs and port numbers differ between the service and development
> version, so I have some environment properties defined in WEB-INF/web.xml
> for the service version and WEB-INF/jetty-env.xml for development.  I can
> access those settings within my java files using eg:
>        String audioLocation = (String)((new
> InitialContext()).lookup("java:comp/env/StreamServerLocation"));
>
> This works fine and means I don't need to change anything when moving my
> development version into service - I just commit to subversion and then
> 'update' the service directory, compile, package and deploy.  Nice and
> simple.
>
> What I'd like to do now, however, is have a way to access other constants
> in those XML files directly from the Tapestry template TML files without
> having to create properties and accessors in Java.
>
> I've tried a number of variations on the following, but nothing works:
>        ${message:comp/env/StreamServerLocation}
>
> Is there any way to do this?
>
> Thanks
> Mark
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to