Why not using the DD? The deployer could specify the language to use...
(however maybe think about your design, a name f.e. is the same in all langs,
mostly its a matter of content which is different, which in turn is related to
the logic of your app)
Markus
Stefan Trcek schrieb:
> Suppose an entity bean has a method, something like
> public String getName();
> The result should be internationalized, i.e. another string for french
> and english. One solution would be to give "getName()" a parameter:
> public String getName(Language lang);
> I'd like to avoid this parameter on every method for every entity
> bean. How do you handle this case?
>
> Stefan
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
