-
Hi all, I have across some implementation: it was an J2EE (EJB) application deployed on an application server. To access (CRUD) data a Singleton class was implemted.
The client usage is something like DO.instance.save(bean);
So, wondering, is it a good idea to use Singleton in this scenario? Please throw some light.
Thanks in advance.
Elangovan. S
-
If its not a good idea its not a bad idea either , I guess the question again comes down to do you need a singleton or not, as you would decide for any other class, the fact that it is used for CRUD operations should not be a criterion in deciding that.
