tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Walter (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Commented: (TAPESTRY-365) Can't access Page Message Catalog without have a page specification file
Date Fri, 01 Jul 2005 19:22:00 GMT
    [ http://issues.apache.org/jira/browse/TAPESTRY-365?page=comments#action_12314914 ] 

Scott Walter commented on TAPESTRY-365:

In my example I have a page ChangedLocale.html in the root of my web app, and have a file
called ChangedLocale.properties in /WEB-INF.  It doesn't work unless I have a page specification

> Can't access Page Message Catalog without have a page specification file
> ------------------------------------------------------------------------
>          Key: TAPESTRY-365
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-365
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 4.0
>     Reporter: Scott Walter

> I have created a page ChangedLocale.html without using a page specification fiile (I
am using annotations).  When I try to get a message from the Page Message Catalog file "ChangedLocale.properties"
which I put in WEB-INF, the message is never found.  On the page I used this to attempt to
get the message:
> <span jwcid="@Insert" value="message:changedlocal"/>
> However if I create a simple page specification file like the one below, it works:
> <page-specification class="com.scottwalter.sandbox.tapestry4.pages.ChangedLocale">
> </page-specification>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message