[jira] Commented: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
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 --%>
>
> <%-- Create the connection manually --%>
>var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571996#action_12571996
]
David Jencks commented on GERONIMO-3875:
I've never understood the thinking behind the DB viewer portlet. I've always
wanted it to use the database pools running in the server rather than
connecting to the database directly. So I would prefer it if the only way to
look at a database was through a running database pool. In any case perhaps if
we keep the current option of direct connection we could have a choice
between direct connection or selecting from an existing pool? I haven't looked
at your patch. I would think that selecting the connection manager or MCF
name would avoid ambiguity.
with this approach would we be able to work with non-derby databases?
> 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
>
> Attachments: GERONIMO-3875.patch
>
>
> 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 --%>
>
> <%-- Create the connection manually --%>
>var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576192#action_12576192
]
Donald Woods commented on GERONIMO-3875:
Looks like a good compromise for now. We can revisit/change the intent of this
portlet in trunk via a different JIRA...
> 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
>
> Attachments: GERONIMO-3875.patch
>
>
> 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 --%>
>
> <%-- Create the connection manually --%>
>var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582628#action_12582628
]
Vamsavardhana Reddy commented on GERONIMO-3875:
---
At revision: 641794 in branches\2.1
At revision: 641795 in trunk
o Enables using DB portlet for databases with connection pools defined.
> 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
>
> Attachments: GERONIMO-3875.patch
>
>
> 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 --%>
>
> <%-- Create the connection manually --%>
>var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619502#action_12619502
]
Michal Borowiecki commented on GERONIMO-3875:
-
I created a patch allowing Run SQL portlet to execute queries against any
datasource (including non-derby): GERONIMO-4225
Making DB Viewer work with non-derby databases will be much trickier, because
it would require a portable way to list database tables (currently a
Derby-specific approach of querying sys.systables is used)
> 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
> Fix For: 2.1.3, 2.2
>
> Attachments: GERONIMO-3875.patch
>
>
> 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 --%>
>
> <%-- Create the connection manually --%>
>var="ds"
> driver="org.apache.derby.jdbc.EmbeddedDriver"
> url="jdbc:derby:${db};create=true"
> user=""
> password=""
> />
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
