on 5/10/01 3:49 AM, "Gareth Coltman" <[EMAIL PROTECTED]> wrote:
> As far as I am aware the Turbine Resource service does not allow resource
> info to be loaded from a database. I think this would be a very useful
> feature. Sometimes property files are not appropriate for all resource
> loading. While I appreciate that a property file would be necessary to
> bootstrap a database resource table, I would love to see a feature like:
>
> include = defaultdatabase.resourcestable
>
> Does this sound like a good idea?
>
> I need to be able to query lookup/reference data for my application and
> store it in the global cache. I am considering either creating a service to
> do this (not sure how to go about this though) or simple creating a utility
> class that would implement some lazy initialisation.
>
> Has any one else designed a lookup system? How did you choose to do it?
>
> Any ideas?
>
> Gareth
Implement the ResourceService interface with your own code. You will
probably also need to implement your own TurbineConfig object as well.
That will allow you to define your properties where ever and how ever you
want.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
