[ http://issues.apache.org/jira/browse/TAPESTRY-645?page=comments#action_12358362 ]
Howard M. Lewis Ship commented on TAPESTRY-645: ----------------------------------------------- I'm having trouble validating this one. I have a page with an HTML template, a Java class, but no page specification, called "Redirect". I have messages in /WEB-INF/Redirect.properties Those messages ARE accessible. Ah, I see what is happening. When there is not page specification, a "virtual page specification" is created, and its location is relative to its namespace. So if you have /WEB-INF/app.application (defining the namespace), the your blah/Page will be /WEB-INF/blah/Page.page and /WEB-INF/blah/Page.properties. The reason what you have worked is that Tapestry will look directly in the context root for a page specification, and the default location for a page's HTML template and message catalog is in the same folder as the page specification. Only if the files are not there does Tapestry do a more exaustive search. > 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]
