The DriverManager is handled by the container, which uses a different classpath than your webapp. If you were to check the logs, you would probably find an error message on startup.
Glad it works, this one got me too for a while. Take care, Ben On Mon, 2002-12-09 at 06:40, Andrey Sadovykh wrote: > Thanks Steve and Benjamin, > > I works!!!! > > I've put JDBC driver to Tomcat/common, and it works. :)))))))))))) > > It's strange that Tomcat falls down without any exception if service can't > find a class. :( > > Best regards, > > Andrey > > ----- Original Message ----- > From: "Steve Loughran" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: 9 ������� 2002 �. 1:57 > Subject: Re: Axis and JDBC example? > > > > I talk to a db, it just works. But I am using hsqlb and i make sure it is > in > > my classpath > > > > ----- Original Message ----- > > From: "Andrey Sadovykh" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Sunday, December 08, 2002 16:25 > > Subject: Axis and JDBC example? > > > > > > > Hello, > > > > > > Can anybody give me working example of AXIS Web Service providing a > > > front-end to a database? > > > > > > My simple Web Service makes Tomcat get down with > java.net.SocketException: > > > Connection reset by peer: JVM_recv in socket input > > > stream read, when I call remote method with JDBC driver intialization. > > > > > > > I wouldnt blame axis for this, more likely your jdbc connection. It may be > > the socket that your driver is using to talk to a db, a socket that isnt > > working. > > > > Have you ever got this jdbc driver to work from a generic webapp in > tomcat? > > > > > > >
