> > A singleton pattern will not be very portable. Even if the static member > were portable which it is not, the use of custom ClassLoaders by most > containers will likely cause issues with your pattern. > It seems it would not be portable only if you want a singleton for all containers in cluster. But a singleton seems very portable and applicable in situations where you want a singleton object per container and do not need to share that singleton between multiple containers. =========================================================================== 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".
