db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Wilder (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-410) ClientDataSource should not require serverName/portNumber to be set
Date Sat, 17 Sep 2005 15:08:55 GMT
     [ http://issues.apache.org/jira/browse/DERBY-410?page=all ]
     
Philip Wilder resolved DERBY-410:
---------------------------------

    Fix Version: 10.1.2.0
                 10.1.1.0
     Resolution: Fixed
      Assign To: Philip Wilder

The July 6, patch addressed the original concerns of this issue. While Dan brought up the
potential issue of null handling (See Derby-406) further investigations appear to indicate
null values are handled appropriately.

> ClientDataSource should not require serverName/portNumber to  be set
> --------------------------------------------------------------------
>
>          Key: DERBY-410
>          URL: http://issues.apache.org/jira/browse/DERBY-410
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.1.1.0, 10.2.0.0
>     Reporter: Kathey Marsden
>     Assignee: Philip Wilder
>      Fix For: 10.1.1.0, 10.1.2.0

>
> the ClientDataSource property  serverName should default to "localhost" but is currently
 required.
> http://incubator.apache.org/derby/docs/adminguide/cadminappsclient.html
> See repro for DERBY-409
> and comment out the lines
> ds.setServerName("localhost");
> ds.setPortNumber(1527);

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message