[ http://issues.apache.org/jira/browse/TAPESTRY-645?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-645:
-------------------------------------------
Resolution: Invalid
> Confusion on where message catalog (.properties files) exist when no
> page/component specification
> -------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-645
> URL: http://issues.apache.org/jira/browse/TAPESTRY-645
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Reporter: Kevin J. Menard, Jr.
> Assignee: Howard M. Lewis Ship
>
> There seems to be an inconsistency with the properties file search procedure.
> If I have something like:
> context/blah/Page.html
> context/blah/Page.page
> context/blah/Page.properties
> then all is good. The .properties file is found and the values pulled out
> appropriately.
> If the .page file is removed, however, the .properties file is not found and
> loaded. Note that in this case, the .page file really contains nothing but
> the bare minimum.
> Since page specs are optional, it seems inconsistent that their presence or
> lack thereof affects the search path for the properties files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
