I agree. But what about contexts? Since I come from Resin, the implementation there is different. The Singleton object is created once for a separate context. Is this an implementation isssue?
----- Original Message ----- From: "Mark Ayad" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 3:45 AM Subject: RE: Virtual Hosts problem with Singleton Class > something your missing > > A Singleton by it's name creates only a single instance of an object (hence > it marshalls object creation i.e. one instance) which is totally acceptable > for a DB connection pool. > > Regards > > Mark > > -----Original Message----- > From: Haris Papadopoulos [mailto:[EMAIL PROTECTED]] > Sent: 18 February 2002 08:38 > To: [EMAIL PROTECTED] > Subject: Virtual Hosts problem with Singleton Class > > > Hi, > I 've configured two virtual hosts under Tomcat 4.0.1 working with Apache > 1.3.20. They both load (on startup) a Servlet which creates a Singleton > object that (in turn) creates a DB pool. Both servlets are defined in the > separate web.xml files. > It seems that the second servlet does not create the pooling object but > instead it gets an Instance of the one created by the first one (strange > enough since they exist in different contexts). > Everything else seems to work in the appropriate virtual host context. Is > this a matter concerning Singleton objects and maybe a bug, or is there > something I 'm missing? > We 're trying to migrate to Tomcat from Resin and I haven't found any > relative info so far regarding this problem. > Thanks in advance. > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
