Alone in the dark... >>>I don't have a reference link now, but I recall >that use of static methods >>>and classes is forbidden in EJB objects, since it >can break the >>>container-component contracts and the JNDI >resolution system. > >>static methods are fine static variables are not >except in very very very >>limited circumstances. >> > >Correct, but each use of a static method hints at a >static var too. > Well in many cases that is true.
Yes but not in the classes i sent. >I need to elaborate my, possibly overstated, point: > Because EJB beans may be in different classloaders, >there may be > more that one instance of a thing the developer >thinks there is only > one of . For some EJB solutions, it may be possible >to live with that. >-ph This is true and this is why i designed a Static class which try to get configuration from JNDI in order to prevent the multiple Singleton phenomena. Is there something wrong with the code i sent? MAG __________________________________________________________ Lèche-vitrine ou lèche-écran ? magasinage.yahoo.ca -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
