Here's a naive architecture/design question about using JNDI, I hope it's not too dumb: I have a singleton class (i.e. it only provides static methods) that I initialize during JBoss startup (using JMX), so that all my EJBeans running in the same VM can use it. This works fine (for now). Question 1: Is this acceptable practice? I see it done other places, though it seems like it makes my beans non-portable to other containers that don't have the same classes provided (or it assumes that I will initiate this singleton class in every VM where my EJBeans exist). Question 2: In what situations would it be preferable to instantiate this class in a way that it could be bound in to JNDI, so that all beans must "look up" a copy of the class? Thanks & cheers, Roger -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
