geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3051) DB Viewer portlet error
Date Mon, 02 Apr 2007 15:26:32 GMT


David Jencks commented on GERONIMO-3051:

I think this is a bug in jstl, it should be using the TCCL.  However unless someone wants
to write geronimo-jstl we probably have to live with it.

Could I ask what bad things happen if you leave the jstl dependency out of jetty-deployer
and tomcat-deployer?  Also, isn't jstl a jsp feature?  If so I would think that the JspModuleBuilderExtension
default environment would be an even better place for the dependency, and it would only have
to go in one place.

> DB Viewer portlet error
> -----------------------
>                 Key: GERONIMO-3051
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, databases
>    Affects Versions: 2.0-M4
>         Environment: embedded Derby databases
>            Reporter: Hernan Cunico
>         Attachments: GERONIMO-3051.patch
> There is a problem when trying to view an embedded Derby database.
> I am able to successfully create a new DB with the DB manager and a new entry appears
in the DB Viewer but when I try to view that DB from the DB Viewer I get a portlet error.
> When I check the logs I get this:
> 09:57:02,421 ERROR [listTables_jsp]] Servlet.service() for servlet jsp.WEB_002dINF.view.internaldb.listTables_jsp
threw exception
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: Error getting connection:
"java.sql.SQLException: No suitable driver"
> ...
> 09:57:02,421 ERROR [[DBViewer]] Servlet.service() for servlet DBViewer threw exception
> javax.servlet.ServletException
> ...
> 09:57:02,453 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching
> javax.portlet.PortletException
> ...
> With the exception of the "SystemDatabase" all the other databases created on the embedded
Derby are also unaccessible from other applications.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message