I agree entirely. A "pointer bean" to the right data in the request. I'm so there.
Thanks Ted. YTH -Joe > -----Original Message----- > From: Tsang, F (Fred) [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 11, 2003 5:06 AM > To: Struts Users Mailing List > Subject: RE: logic tag using locale > > > Thanks Ted, > > Doesn't this mean creating another bean/object though? For > instance, right now I have two fields in the object that have > this sort of requirement (ie. there are about 12 fields that > don't have a language requirement). I was thinking it would > be more efficient to just let the tile/jsp do the > presentation work. You could be right though... maybe a > simple presentation bean that just handles internationalised fields. > > cheers, > Fred > > -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: 10 December 2003 20:04 > To: Struts Users Mailing List > Subject: Re: logic tag using locale > > > I'd suggest resolving this type of language choice in the Action. For > example, there could be one product bean that is populated > with whatever > > language is preferred by the client. The page could then just write > whatever has been placed into the bean. > > HTH, Ted. > _____________________________________________________________ > > This email (including any attachments to it) is confidential, > legally privileged, subject to copyright and is sent for the > personal attention of the intended recipient only. If you > have received this email in error, please advise us > immediately and delete it. You are notified that disclosing, > copying, distributing or taking any action in reliance on the > contents of this information is strictly prohibited. Although > we have taken reasonable precautions to ensure no viruses are > present in this email, we cannot accept responsibility for > any loss or damage arising from the viruses in this email or > attachments. We exclude any liability for the content of this > email, or for the consequences of any actions taken on the > basis of the information provided in this email or its > attachments, unless that information is subsequently > confirmed in writing. If this email contains an offer, that > should be considered as an invitation to treat. > _____________________________________________________________ > > --------------------------------------------------------------------- > 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]
