[ http://issues.apache.org/jira/browse/TAPESTRY-645?page=all ]
Howard M. Lewis Ship updated TAPESTRY-645:
------------------------------------------
Summary: Confusion on where message catalog (.properties files) exist when
no page/component specification (was: Properties file search procedure)
I believe that when the page specification doesn't exist, the properties files
will be located relative to the class file, but I'll check. The meta question
is whether that is correct or not.
To be honest, the direction I want to go with the framework is that the page
name is more or less directly named to a Java class (within a package) and the
page specification is an add-on, on top of annotation within that class. In
addition, the message catalog would then more sensibly always be associated
with the class. The case where you have a page, with a specification, but not
Java class, would be the exception to the rule ... today Tapestry treats that
as the normal case, when it isn't.
> 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]
