RE: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-06 Thread MWick
> From: Daniel Mikusa [mailto:dmik...@gopivotal.com] > Sent: Monday, August 05, 2013 7:56 AM > To: Tomcat Users List > Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 > > On Aug 4, 2013, at 2:14 PM, mw...@loftware.com wrote: > > >> From

Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-05 Thread Daniel Mikusa
On Aug 4, 2013, at 2:14 PM, mw...@loftware.com wrote: >> From: Mark Eggers [mailto:its_toas...@yahoo.com] >> Sent: Friday, August 02, 2013 5:28 PM >> To: Tomcat Users List >> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 >> >> On 8/2/20

RE: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-04 Thread MWick
> From: Mark Eggers [mailto:its_toas...@yahoo.com] > Sent: Friday, August 02, 2013 5:28 PM > To: Tomcat Users List > Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 > > On 8/2/2013 1:30 PM, mw...@loftware.com wrote: > >> From: Michael-O [mailto:1983-

Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-02 Thread Mark Eggers
On 8/2/2013 1:30 PM, mw...@loftware.com wrote: From: Michael-O [mailto:1983-01...@gmx.net] Sent: Friday, August 02, 2013 3:28 PM To: Tomcat Users List Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 Am 2013-08-02 21:24, schrieb mw...@loftware.com: I expect that by putting the

RE: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-02 Thread MWick
> From: Michael-O [mailto:1983-01...@gmx.net] > Sent: Friday, August 02, 2013 3:28 PM > To: Tomcat Users List > Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 > > Am 2013-08-02 21:24, schrieb mw...@loftware.com: > > I expect that by putting the SQL

Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35

2013-08-02 Thread Michael-O
Am 2013-08-02 21:24, schrieb mw...@loftware.com: I expect that by putting the SQL Server JDBC4 driver jar (sqljdbc4.jar) into ${CATALINA_HOME}/lib, that the driver would be automatically available upon server start. As expected, this works in 6.0.33, but fails in 6.0.35. It seems that the fix t