Thanks for the reply,
I understand your solution and am defintely gonna be trying to implement
this. In our case, it isnt exactly the country example, but a whole lot of
different attributes.
However, I understand that creating separate beans for logical entities in
the table will be useful.
>For large countries you may choose to divide again, e.g. for the USA you
>may
>have beans for individual states, note that
>if you update the backend DB data it won't be reflected in the bean until
>it's re-instantiated
Whenever the backend DB data is updated, we could trigger the refreshing of
the servlet context where the beans sit. This will enable the refreshing of
the bean. But maintaining the concurrency of data will be an issue. One way
of solving this could be the use of 'synchronized block'. any pointers /
suggestions?
thanks again,
vini
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
