-Original Message-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 8:23 AM
To: struts
Subject: ActionMessage replacement keys ?
hihi all,
is everyone rolling their own helper function to use other
message keys
as replacement values when creating
For the 99.9% of the situations I agree with you Jim, but when you do some
kind of generic subsystem to reuse across applications it's very possible
to need such behavior. Here might be arguable that such situations can be
avoided, but still... you might end up presenting messages that are
-Original Message-
From: Radu Badita [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 9:12 AM
To: Struts Users Mailing List
Subject: RE: ActionMessage replacement keys ?
For the 99.9% of the situations I agree with you Jim, but
when you do some
kind of generic
In some cases you may be able to use the choice formatter. It
won't work in every case, but if say you are looking up a
day-of-the-week name to use in a sentence, you might be able to pull
it off:
shipdate.warning=Your thing will ship on
hi Jim!
but i think most of the time when there needs to be a replacement
value, that value is in the form of a noun (at least that's how my
messages are). so given a message with replacement placeholders,
wouldn't the only issue be the placement (position) of these
placeholders within the
At 9:43 AM -0800 12/21/04, Woodchuck wrote:
doesn't it seem odd that ActionMessage doesn't already have the ability
to use other keys as replacement values... i can't think of any reason
for this other than it was simply forgotten
Well, it's more complicated than that - is it safe to assume that
-Original Message-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 10:43 AM
To: Struts Users Mailing List
Subject: RE: ActionMessage replacement keys ?
hi Jim!
but i think most of the time when there needs to be a replacement
value, that value
that reminds me, you have to check this site out, it is hilarious:
http://www.engrish.com
have fun! :D
woodchuck
--- Jim Barrows [EMAIL PROTECTED] wrote:
Somebody set up us the bomb! All your base are belong to us!
now
that would be a major translation problem. no argument here.
but i also see your point. just having one unique message for each
unique situation is simple and does the job. the only negative thing
is that it takes up more memory when the message bundle is cached in
application scope since there will be a lot of duplication in the
bundle.
i was
that's true. i wouldn't like to have the code assume which bundle
either.
but now in hindsight, perhaps one bundle per language would be better
than having the ability to specify many different bundles (per
language). because in the end, all of the message keys would work just
as well if they
At 10:55 AM -0800 12/21/04, Woodchuck wrote:
that's true. i wouldn't like to have the code assume which bundle
either.
but now in hindsight, perhaps one bundle per language would be better
than having the ability to specify many different bundles (per
language). because in the end, all of the
11 matches
Mail list logo
