[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571930#action_12571930
]
Vamsavardhana Reddy commented on GERONIMO-3875:
-----------------------------------------------
Option 1: We can search in the connection pools to see if we can obtain a data
source matching the database name. Will not work for creating new databases
from console. Will not work for databases with no associated DatabasePools.
May not work properly if there is more than one Database Pool with same
database name.
Option 2: Require the user to enter credentials for db authentication, say once
per session.
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> -------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3875
> URL: https://issues.apache.org/jira/browse/GERONIMO-3875
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1, 2.1.1, 2.2
> Environment: Win XP, G 2.1 Tomcat
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: 2.1.1, 2.2
>
>
> After enabling authentication for Derby, I am noticing that DB Viewer
> portlet is unable to work with any database other that SystemDatabase.
> listTables.jsp has the following code:
> {code}
> <%-- Datasource --%>
> <c:if test="${ds == null}">
> <%-- Create the connection manually --%>
> <sql:setDataSource
> var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
> </c:if>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
