db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.
Date Thu, 22 Sep 2005 03:29:42 GMT
Kathey Marsden wrote:

> Deepa Remesh wrote:

>>I am doing the following. In network server, check if a null
>>connection is returned by InternalDriver. If so, throw "new
>>SQLException("No suitable driver","08001");" to match behaviour with
>>embedded driver. The server will use this SQLException to build
>>RDBAFLRM and SQLCARD and send it to client.
>>
>>When using embedded driver, this exception gets thrown by
>>DriverManager.getConnection method.
>> 
>>
> 
> 
> Hi Deepa,
> 
> That sounds like the correct approach except that we need to localize
> the message.
> Since this message comes from the server message file instead of the
> network server message file,  I think we need to  use  one of the 
> org.apache.derby.impl.jdbc.Util.generateCsSQLException   methods.

Is that correct? The error is being thrown by the network server as
Deepa describes, not the embedded engine. The embedded driver is
correctly returning null here, it's the network server that needs to
handle the null.

Dan.


Mime
View raw message