If I wanted to have the equivalent of a whole table of data, liek the names of U.S. states, cached in a J2EE application, liike in the EJB container, and I wanted this data available to every EJB that wanted it, what would be a good design approach? A plain Java object implemented as a SIngleton? A stateful session bean with ahandle taht any caller could lookup and use? If the latter, how would you get around the restriction against multiple callers on an EJB? Thanks.
Ken =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
