It would be easier for you to move to hibernate then to come up with
an ideal temporary solution.

Seems you are mixing data sources, data based logic and caching of data.
You may want to relook at your design.

The other idea is you just look at the hibernate code and determine
how you want to design your application. I would start by seperating
storing the datasource in your factory and make that hidden behind a
locator type pattern where it either gets it from cache or from a
factory.

The other thing I would do is to have a similar approach to the data
access by seperating the caching logic. The data access probably
shouldn't care if it is cache or not, leave that to the people using
the dataaccess object.

Those are some thoughts, hope they help.

Dan



On 10/4/05, SUBSCRIBE EJB-INTEREST anonymous <ahtwog@(protected):
> Hi,
> I am not using hibernate now.However,I am planning to use in future.
> If there is a temp solution to tune the below code , let me know as I have
> to use the current code till I move to hibernate.
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
>

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)