Nope, no dupes. Just checked to make sure.
For the most part, I'm referencing these with the @Message annotation,
so there's really no code to show. I do have a couple of calls to
getMessages().format and getMessages().getMessage, but the surrounding
code is quite project specific. I'm basically using these mechanisms in
the most boring way possible :)
As for dir structure, it's something like:
webapp.war/
/WEB-INF/
myapp.application
myapp.properties
mypage.html
mypage.properties
mycomponent.html
mycomponent.properties
We use annotations heavily, so we have very few .page and .jwc files.
Hope this helps (though I bet it doesn't :P ).
jeff
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 06, 2005 9:51 AM
To: Tapestry users
Subject: RE: Application wide namespace message catalog broken?
Has anyone gotten this to work in 3.x??
Jeff, here's a somewhat silly question...do you have duplicate messages
in
both the app & component properties files? I just want to be sure, in
case your code is picking up the component messages first, rather than
the
app messages. I'd ask you for a snipet of code, but the catalog is
really
so easy & obvious. That's why I think this is broken in 3.0.3.
However,
if you feel moved to provide a code snipet or screenshot of your dir
structure, it may help.
Thanks,
- Mike
"Jeff Lubetkin" <[EMAIL PROTECTED]>
12/05/2005 01:26 PM
Please respond to
"Tapestry users" <[email protected]>
To
"Tapestry users" <[email protected]>
cc
Subject
RE: Application wide namespace message catalog broken?
I'm using this functionality in a 4.0-beta-13 app with no issues. I
have messages in both the <application>.properties and
<component>.properties files. My application property file is in
/WEB-INF with my application specification.
jeff
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 1:04 PM
To: Tapestry users
Subject: Re: Application wide namespace message catalog broken?
I and another person on this list are having the same problem. I'm
using
3.0.3.
Has anyone gotten it to *work*??
Ryan <[EMAIL PROTECTED]>
12/03/2005 06:02 PM
Please respond to
"Tapestry users" <[email protected]>
To
Tapestry users <[email protected]>
cc
Subject
Application wide namespace message catalog broken?
I am attempting to use a global application.properties file to specify
the translations for localized strings in my component files but so
far I have not been able to get tapestry to perform as documented.
For more background information on what I am referring to see the
following documentation and closed jira issue:
http://jakarta.apache.org/tapestry/UsersGuide/localization.html (see
Namespace message catalogs)
http://issues.apache.org/jira/browse/TAPESTRY-242
I am using tapestry 4 beta13, here is a little bit about my setup. I
have myapp.application and in the same directory (WEB-INF)
myapp.properties which includes name/value pairs. Inside of a
component I am trying to translate some text using:
getMessages().getMessage(key)
I have verified the key exists in myapp.properties however the result is
[KEY].
Am I using this feature incorrectly or is this a tapestry bug? I was
not able to find anything in jira besides tapestry-242.
Thanks!
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
