each component is a resource bundle, not a model. you can use
component's getstring(..) to read any resource you want.

-igor

On Fri, Mar 13, 2009 at 4:19 AM, Daniel Ferreira Castro
<[email protected]> wrote:
> I have seen some examples of Pages that uses the StringResourceModel to read
> properties inside property files.  But the examples that I saw shows that I
> need to create a StringResourceModel for each property that is inside my
> property file.  So, If I have a Login page that have 3 properties, like
> login.username , login.password and login.button I must create also 3
> StringResourceModels and use each one on the constructor of the Labels.
>
> I do not think it is a practical solution because I see the
> StringResourceModel as a ResourceBundle.
>
> Am I right?  What is the real deal when using it?
> Is it the propper way to internationalize a resource?
> Is there a way to make a single StringResourceModel and use it to read a
> property file so, instead of creating several resources I create a single
> one and pass the key that I wanna retrieve its value?
>
> --
> "Two rules to succeed in life:
> 1 - don´t tell people everything you know."
> --------
> We shall go on to the end.
> We shall fight in France
> We shall fightover the seas and oceans.
> We shall fight with growing confidence and growing strength in the air.
> We shall defend our island whatever the cost may be
> We shall fight on beaches, we shall fight on the landing grounds,
> We shall fight in the fields and in the streets,
> We shall fight on the hills.
> We shall never surrender.
> Winston Churchill
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to