[ http://issues.apache.org/jira/browse/TAPESTRY-645?page=comments#action_12358378 ]
Kevin J. Menard, Jr. commented on TAPESTRY-645: ----------------------------------------------- Okay, so the search procedure is well-defined, but it still feels wrong to me. I see what you're saying with making the page spec and add-on, I just thought we were already there with annotations. With annotations, the page spec already is losing its significance. This case outlined here seems to violate the page spec is optional idea. I suspect many (and I have seen them on the list) people are going to be unpleasantly surprised to find their i18n stuff broken because they replaced a page spec with annotations. Without knowing a terrible amount about how Tapestry is doing things under the hood, it seems to me that if the search procedure followed the same rules for finding template files, then the problem would go away. At this point, should I open an RFE? > 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]
