[
https://issues.apache.org/jira/browse/TAPESTRY-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Menard reopened TAPESTRY-645:
-----------------------------------
After this debacle I had decided it was just easier to dump i18n and sorta
forgot about the whole thing.
Fast forward a couple years and now I have no page specs and started using
BeanForm, which requires the use of message catalogs. I placed a properties
file in four different locations trying to figure out where it was supposed to
go before recalling this issue. Can someone please reinvestigate its validity?
It seems a bit foolish to me that if I have the following structure:
context/
context/store
context/support
context/WEB-INF
that I have to mirror the entire structure of context under WEB-INF just to
have my properties files found. The page templates are picked up fine off the
various context subdirectories, so why can the properties files?
> Confusion on where message catalog (.properties files) exist when no
> page/component specification
> -------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-645
> URL: https://issues.apache.org/jira/browse/TAPESTRY-645
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Reporter: Kevin Menard
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
