Bugzilla – Full Text Bug Listing
| Summary: | "user" property in DatasourceLogin not removed when calling setUsername(null) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | David Minsky <david.minsky> | ||||
| Component: | Eclipselink | Assignee: | David Minsky <david.minsky> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Project Inbox <eclipselink.foundation-inbox> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
6117441 Created attachment 199215 [details]
Proposed patch and testcase
Fixed in trunk (2.4) at revision: 9733 2.3.1 checkin pending Checked into 2.3.1 at r9746 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
DatasourceLogin is initialized with a default "user" property and an empty ("") username. Some drivers don't like the "user" and "password" properties, and therefore these should be easily removable from the DatasourceLogin's internal properties (passed at runtime to the driver/DS). Problem: 1. Calling DatasourceLogin >> setUserName(null) does not remove the "user" property from the internal properties, and therefore the property is still passed at runtime. Inconveniently the following workaround must be used instead: DataSourceLogin.getProperties().remove("user"); 2. Calling DatasourceLogin >> setPassword(null) removes the "password" property from the internal properties, so there is an element of inconsistency to the way that this works currently. Proposing that calling DatasourceLogin >> setUserName(null) remove the "user" property from the DatasourceLogin's internal properties list.