Abstract EJBHome lookup codes into reusable EJBHomeFactory, that can cache EJBHome for the lifetime of a client application.
Albert Pi Corp IS System Delivery 516-803-3762 >>> "David M. Karr" <[EMAIL PROTECTED]> 07/30/02 11:39AM >>> This is really a general question about issues between using the standard "singleton" pattern, versus a "static utility" class, in the context of the EJB environment. In particular, is there a problem with designing an EJBHomeFactory class which consists of just static synchronized methods, as opposed to just having a static "getInstance()" method and a private static "EJBHomeFactory" instance? -- =================================================================== David M. Karr ; Java/J2EE/XML/Unix/C++ [EMAIL PROTECTED] =========================================================================== 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". ==========================================================================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".
