geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1532) NullPointerException when a badly named jar is put into repository directory
Date Thu, 06 Apr 2006 19:13:35 GMT
     [ ]

Dain Sundstrom updated GERONIMO-1532:

      Component: console
    Fix Version: 1.1
      Assign To: Aaron Mulder

My guess is you have already fixed this.

> NullPointerException when a badly named jar is put into repository directory
> ----------------------------------------------------------------------------
>          Key: GERONIMO-1532
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console
>     Versions: 1.0
>     Reporter: Heikki Linnakangas
>     Assignee: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.1
>  Attachments: listURIs.diff
> I copied a JDBC driver jar to geronimo/repository-directory, thinking that geronimo would
pick it up from there. What I didn't know, is that jars in the repository need to be named
in a particular way.
> I then tried to add a Database pool using the wizard. I filled the name and type in step
1, and clicked next. Instead of step 2, I got a blank screen, and this stack trace in the
> 14:30:33,322 ERROR [DatabasePoolPortlet] Unable to render portlet
> java.lang.NullPointerException
> 	at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.loadDriverJARList(
> 	at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.renderBasicParams(
> 	at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.doView(
> 	at javax.portlet.GenericPortlet.doDispatch(
> 	at javax.portlet.GenericPortlet.render(
> ...
> The culprit seems to be the FileSystemRepository.listURIs-method, that doesn't handle
invalid filenames properly, but returns nulls in the array it returns instead.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message