geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Resolved: (GERONIMO-1382) DB Pool Portlet blows up on empty username/password
Date Sun, 08 Jan 2006 15:15:22 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1382?page=all ]
     
Aaron Mulder resolved GERONIMO-1382:
------------------------------------

    Resolution: Fixed

Pretty sure this was fixed in the run-up to 1.0.

> DB Pool Portlet blows up on empty username/password
> ---------------------------------------------------
>
>          Key: GERONIMO-1382
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1382
>      Project: Geronimo
>         Type: Bug
>   Components: console, deployment
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.0

>
> If you leave the username and/or password empty on the database pool portlet, that is
translated to a value of "null".  Currently, the JSR-88 connector implementation attempts
to write XML with "nil=true" or something to that effect, which is not valid for the schemas.
 Instead, we need to omit those config property setting elements.  This is a little complex
because we attempt to keep a set of config property setting elements that maps 1:1 to the
config settings available in ra.xml, so we don't want to permanently delete missing elements
when you save or something like that.
> Also, the DB pool portlet itself gets an NPE on line 789 or so when the username or password
is null and it tries to put that into a Hashtable to connect.

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