V8 Application Level Caching (Singleton Object_?

Question

I have a requirement to have our data base lookups cached in an object which is
shared for all sessions accessing the application. Normally this would be accomplished
via a singleton object. Howerver in the spirit of bea v8, I would like to use
V8 controls to populate the caches.
I have created a control called LookupImpl and a database control called LookupDB.
LookupDB is a member variable of LookupImpl. LookupImpl has an init() method
which will retrieves data from LookupDB and caches it for later use.
If I place LookupImpl on a page flow it works fine. But if I manually instantiate
LookupImpl (x = new LookupImpl())) in a java class (my singleton class intended
to share one copy of the information among all users) , when LookupImpl tries
to run a method on its LookupDB member variable, the member variable is null and
the process blows up.
I have also read in an article
http://dev2dev.bea.com/products/wlworkshop81/articles/wlw_internals.jsp
stating that controls cannot be manually instantiated.
So my questions are:
What would be the best practice for doing sharing application level cached data?
It is true that a java class cannot instantiate controls?
Can a control be defined to be a “singleton”?
Thanks for all input
gr

Answer 1

I have a requirement to have our data base lookups cached in an object
which is shared for all sessions accessing the application. Normally this
would be accomplished via a singleton object. Howerver in the spirit of
bea v8, I would like to use V8 controls to populate the caches.That's an odd approach. Normally you'd have a singleton, hang a cache object
in the JNDI tree, or even have an EJB that handled this task.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"gerry rodman" <[email protected]> wrote in message
news:3fcfb309$[email protected]..
>