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] Commented: (DERBY-406) Client DataSource should not require user property to be set
Date Wed, 06 Jul 2005 19:55:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315172 ] 

Philip Wilder commented on DERBY-406:
-------------------------------------

"Existing data sources do not have any properties that have a default."

Perhaps I am misunderstanding your comment. While EmbeddedSimpleDataSource did not have any
default values ClientCaseDataSource is more of a mixed bag. There already existed propertyDefaults
for  loginTimeout, portNumber, securityMechanism, retrieveMessageText and others. Even user
had a propertyDefault of "APP" prior to the patch, it was simply not set. 

This said I acknowledge that it is an ongoing derby goal to have Client functionality more
closely match Embedded. However, if this is the case then it might be necessary to undo considerably
more then just user and servername. 

> Client DataSource should not require user property to be set
> ------------------------------------------------------------
>
>          Key: DERBY-406
>          URL: http://issues.apache.org/jira/browse/DERBY-406
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions: 10.1.1.0, 10.2.0.0
>     Reporter: Kathey Marsden
>     Assignee: Philip Wilder
>  Attachments: DataSourceNoUser.java, Derby406_409_410.patch
>
> ClientDataSource should not require user to be set.  It should default to user APP as
described in:
> http://incubator.apache.org/derby/docs/adminguide/cadminappsclient.html
> This all seems to work ok for for DriverManager connections but fails for ClientDataSource

> run the attached repro 
> $ java DataSourceNoUser
> embedded no userid/password
> client userid/password set
> client no password
> client no userid/no password
> org.apache.derby.client.am.SqlException: null userid not supported
>         at org.apache.derby.client.net.NetConnection.checkUser(NetConnection.java:998)
>         at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:380)
>         at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:233)
>         at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:201)
>         at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:156)
>         at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:135)
>         at DataSourceNoUser.main(DataSourceNoUser.java:42)

-- 
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