Re: SQL Server Driver and Classpath problem
Re: SQL Server Driver and Classpath problem
- Subject: Re: SQL Server Driver and Classpath problem
- From: Peter Vandoros <email@hidden>
- Date: Mon, 8 Sep 2008 09:42:19 +1000
That was it. I never would have found that because for SQL Server
2000 I never had to populate a value for "driver" in my connection
dictionary. It always worked just with the url. I don't really
understand why that changed or, better, why the adaptor was looking
for another driver signature but I am just glad it worked and saved
my sanity.
I believe the SQL Server JDBC Plug In that comes with WebObjects is
old and defines the default driver class name for SQL Server 2000 (and
below?) if one is not specified. I always define all the model
connection dictionary properties just to make sure I am always using
the correct properties.
Thanks much for your help!!
No problem :)
Regards
Peter Vandoros
Software Engineer
Etech Group Pty Ltd
Level 3/21 Victoria St
Melbourne VIC 3000
Australia
Ph: +61 3 9639 9677
Fax: +61 3 9639 9577
----------------------------------
IMPORTANT: This e-mail message and any attachments are confidential
and may be privileged. If received in error, please reply to this
message and destroy all copies and any attachments. You should check
this message and any attachments for viruses or defects. Our liability
is limited to resupplying any affected message or attachments. For
more information about Etech Group, please visit us at http://www.etechgroup.com.au
.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden