Scratch that - I had forgotten that when using classes as bundles you  
need to use the FQCN

Cheers, Tim

Sent from my iPhone

On 25 Feb 2009, at 17:07, Tim Perrett <[email protected]> wrote:

>
> Thanks for your reply Marius - I made a trial class, but I'm unable to
> get lift to use it as a resource bundle? I have a basic bundle with
> some strings (definded in a class), from here, how would one tell lift
> about it's existance?
>
> Cheers
>
> Tim
>
> On Feb 25, 4:01 pm, "marius d." <[email protected]> wrote:
>> On Feb 24, 10:16 pm, Tim Perrett <[email protected]> wrote:
>>
>>> Guys,
>>
>>> Just looking for a sanity check. Im planning out some database
>>> localization stuff that I need to implement to localize a  
>>> system... Im
>>> not concerned with currency or other such fun localization problems,
>>> simply localizing text in my database.
>>
>>> Right now, im thinking of just creating a custom ResourceBundle and
>>> having it populated by / accessing content that i'll hold in an in-
>>> memory LRU cache (something like net.liftweb.util.KeyedCache). As I
>>> wont need to worry about other issues like currency, im guessing  
>>> that
>>> if I add this LiftRules.resourceNames then lift will look at it for
>>> localized content?
>>
>> LiftRules.resourceNames is just a list of strings and if you abstract
>> the ResourceBundle it can have a slightly different semantic then
>> right now where we use the ResourceBundle in the "traditional" way.  
>> It
>> the DB context those names can act as a "namespace".
>>
>>
>>
>>> Is their any hope of such a simplistic scheme working or have I just
>>> been awake too long today?!
>>
>>> Cheers
>>
>>> Tim
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to