[jira] Closed: (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:all-tabpanel
]
David Jencks closed GERONIMO-3875.
--
Resolution: Fixed
We have the use pools approach, I think that's enough.
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.1.3, 2.1.4, 2.2
Environment: Win XP, G 2.1 Tomcat
Reporter: Vamsavardhana Reddy
Fix For: 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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Jarek Gawor updated GERONIMO-3875:
--
Affects Version/s: 2.1.4
Fix Version/s: (was: 2.1.4)
Updating versions as it probably will not get fixed for 2.1.4.
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.1.3, 2.1.4, 2.2
Environment: Win XP, G 2.1 Tomcat
Reporter: Vamsavardhana Reddy
Assignee: Donald Woods
Fix For: 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 --%
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.
[jira] Assigned: (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:all-tabpanel
]
Donald Woods reassigned GERONIMO-3875:
--
Assignee: (was: Donald Woods)
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.1.3, 2.1.4, 2.2
Environment: Win XP, G 2.1 Tomcat
Reporter: Vamsavardhana Reddy
Fix For: 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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Donald Woods updated GERONIMO-3875:
---
Affects Version/s: 2.1.3
Fix Version/s: (was: 2.1.3)
2.1.4
Assignee: Donald Woods
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.1.3, 2.2
Environment: Win XP, G 2.1 Tomcat
Reporter: Vamsavardhana Reddy
Assignee: Donald Woods
Fix For: 2.1.4, 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 --%
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.
[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-tabpanelfocusedCommentId=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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Joe Bohn updated GERONIMO-3875:
---
Fix Version/s: (was: 2.1.x)
2.1.2
It looks like fixes were checked in for this in branches/2.1 (2.1.2).Can
this be closed?
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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Joe Bohn updated GERONIMO-3875:
---
Fix Version/s: (was: 2.1.2)
2.1.3
I see that there are comments about more work necessary . so I guess I'll
move it to 2.1.3
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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Joe Bohn updated GERONIMO-3875:
---
Fix Version/s: (was: 2.1.1)
2.1.x
moving fix version to 2.1.x and 2.2 doesn't look like it will make 2.1.1
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.x, 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 --%
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.
[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-tabpanelfocusedCommentId=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 --%
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.
[jira] Updated: (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:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-3875:
--
Assignee: (was: Vamsavardhana Reddy)
I don't think I will get a chance, before branching for 2.1.1, to work on
enabling collection of userid/password from console for creation of new
databases and databases without connection pools defined.
Unassigning so that someone else can pickup where I left off in case it can be
made into 2.1.1.
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.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 --%
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.
[jira] Created: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
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.
[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-tabpanelfocusedCommentId=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.
[jira] Updated: (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:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-3875:
--
Attachment: GERONIMO-3875.patch
GERONIMO-3875.patch: Crude implementation of Option1 from above. Patch created
against branches\2.1.
Comments? Suggestions??
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 --%
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.
[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-tabpanelfocusedCommentId=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 --%
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.
SystemDatabase
I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
IIRC, the derby.log was always in the bin directory. But then again, I could be wrong. Cheers Prasad On 3/2/07, Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
When I paid attention to this some time last year, it was in var\derby directory and derby.log was not turned on by default. Wonder if this is caused by a change in derby itself? Lin Prasad Kashyap wrote: IIRC, the derby.log was always in the bin directory. But then again, I could be wrong. Cheers Prasad On 3/2/07, Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
Re: SystemDatabase
A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. Thanks Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: SystemDatabase
Eh... thats broke... --jason On Mar 2, 2007, at 12:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. Thanks Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek __ __ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com __ __ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: SystemDatabase
On Mar 2, 2007, at 3:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. I'm not following you, Anita. If derby log and systemdatabase are not in var/derby, would someone please create a jira? looks good in M3, at least on my system. --kevan
Re: SystemDatabase
Done. https://issues.apache.org/jira/browse/GERONIMO-2926 Thanks Anita --- Kevan Miller [EMAIL PROTECTED] wrote: On Mar 2, 2007, at 3:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. I'm not following you, Anita. If derby log and systemdatabase are not in var/derby, would someone please create a jira? looks good in M3, at least on my system. --kevan Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know.
Re: Connecting to SystemDatabase and create table
Just go here http://wiki.apache.org/geronimo, create an account, and then you can edit the wiki. The wiki contains help information on how to add new pages, format pages, and so on. -dain -- Dain Sundstrom Chief Architect Gluecode Software On Apr 19, 2005, at 12:32 PM, Katia Aresti Gonzalez wrote: I dont know how to do it :-( From: Dain Sundstrom [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Connecting to SystemDatabase and create table Date: Mon, 18 Apr 2005 08:57:12 -0700 Katia, This is great information. Can you add it to the wiki so others can find it easily? Thanks, -dain -- Dain Sundstrom Chief Architect Gluecode Software On Apr 16, 2005, at 5:50 PM, Katia Aresti Gonzalez wrote: Hello! To connect to the SystemDatabase, and be able to continue with the cmp deployment, just follow these steps: (Windows) 1º STEP a folder with these 3 jars inside: 1. db2jcc.jar 2. db2jcc_license_c.jar you download from IBM site: Derby does not currently provide a network JDBC driver, therefore you must download the IBM DB2 Universal Driver: http://www-106.ibm.com/developerworks/db2/downloads/jcc/ 3. derbytools.jar you get it from the http://incubator.apache.org/derby/derby_downloads.html. Just download derby, unzip, and there is the tool!!! 2º STEP: Create a derby.bat: set classpath=%the folder where you have the 3 jars% java -cp derby.jar;derbynet.jar;derbytools.jar;db2jcc.jar; db2jcc_license_c.jar -Dij.driver=com.ibm.db2.jcc.DB2Driver -Dij.user=system -Dij.password=manager -Dij.protocol=jdbc:derby:net://localhost:1527/ org.apache.derby.tools.ij pause This derby.bat goes in the same folder where you have the jars. 3ºSTEP run the derby.bat, and if everything is ok, you will get in your command line: ij To connect to the SystemDatabase, Geronimo must be running!!! just type: ij CONNECT 'jdbc:derby:net://localhost:1527/SystemDatabase'; ij create table gente (nombre varchar(50)); 0 rows inserted/updated/deleted thats all!!! thanks!! Katia Acepta el reto MSN Premium: Envía hasta 500 megas diarios de fotos desde Hotmail. Descárgalo y pruébalo 2 meses gratis. Recibe ofertas de empleo adaptadas a tu perfil. Introduce tu CV en MSN Empleo.
Re: Connecting to SystemDatabase and create table
I dont know how to do it :-( From: Dain Sundstrom [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Connecting to SystemDatabase and create table Date: Mon, 18 Apr 2005 08:57:12 -0700 Katia, This is great information. Can you add it to the wiki so others can find it easily? Thanks, -dain -- Dain Sundstrom Chief Architect Gluecode Software On Apr 16, 2005, at 5:50 PM, Katia Aresti Gonzalez wrote: Hello! To connect to the SystemDatabase, and be able to continue with the cmp deployment, just follow these steps: (Windows) 1º STEP a folder with these 3jarsinside: 1. db2jcc.jar 2. db2jcc_license_c.jar you download from IBM site: Derby does not currently provide a network JDBC driver, therefore you must download the IBM DB2 Universal Driver: http://www-106.ibm.com/developerworks/db2/downloads/jcc/ 3. derbytools.jar you get it from the http://incubator.apache.org/derby/derby_downloads.html. Just download derby, unzip, and there is the tool!!! 2º STEP: Create a derby.bat: set classpath=%the folder where you have the 3 jars% java -cp derby.jar;derbynet.jar;derbytools.jar;db2jcc.jar;db2jcc_license_c.jar -Dij.driver=com.ibm.db2.jcc.DB2Driver -Dij.user=system -Dij.password=manager -Dij.protocol=jdbc:derby:net://localhost:1527/ org.apache.derby.tools.ij pause This derby.bat goes in the same folder where you have the jars. 3ºSTEP run the derby.bat, and if everything is ok, you will get in your command line: ij To connect to the SystemDatabase, Geronimo must be running!!! just type: ij CONNECT 'jdbc:derby:net://localhost:1527/SystemDatabase'; ij create table gente (nombre varchar(50)); 0 rows inserted/updated/deleted thats all!!! thanks!! Katia Acepta el reto MSN Premium: Envía hasta 500 megas diarios de fotos desde Hotmail. Descárgalo y pruébalo 2 meses gratis. Recibe ofertas de empleo adaptadas a tu perfil. Introduce tu CV en MSN Empleo.
Re: Connecting to SystemDatabase and create table
Katia, This is great information. Can you add it to the wiki so others can find it easily? Thanks, -dain -- Dain Sundstrom Chief Architect Gluecode Software On Apr 16, 2005, at 5:50 PM, Katia Aresti Gonzalez wrote: Hello! To connect to the SystemDatabase, and be able to continue with the cmp deployment, just follow these steps: (Windows) 1º STEP a folder with these 3 jars inside: 1. db2jcc.jar 2. db2jcc_license_c.jar you download from IBM site: Derby does not currently provide a network JDBC driver, therefore you must download the IBM DB2 Universal Driver: http://www-106.ibm.com/developerworks/db2/downloads/jcc/ 3. derbytools.jar you get it from the http://incubator.apache.org/derby/derby_downloads.html. Just download derby, unzip, and there is the tool!!! 2º STEP: Create a derby.bat: set classpath=%the folder where you have the 3 jars% java -cp derby.jar;derbynet.jar;derbytools.jar;db2jcc.jar;db2jcc_license_c.jar -Dij.driver=com.ibm.db2.jcc.DB2Driver -Dij.user=system -Dij.password=manager -Dij.protocol=jdbc:derby:net://localhost:1527/ org.apache.derby.tools.ij pause This derby.bat goes in the same folder where you have the jars. 3ºSTEP run the derby.bat, and if everything is ok, you will get in your command line: ij To connect to the SystemDatabase, Geronimo must be running!!! just type: ij CONNECT 'jdbc:derby:net://localhost:1527/SystemDatabase'; ij create table gente (nombre varchar(50)); 0 rows inserted/updated/deleted thats all!!! thanks!! Katia Acepta el reto MSN Premium: Envía hasta 500 megas diarios de fotos desde Hotmail. Descárgalo y pruébalo 2 meses gratis.
Connecting to SystemDatabase and create table
Hello! To connect to the SystemDatabase, and be able to continue with the cmp deployment, just follow these steps: (Windows) 1º STEP a folder with these 3jarsinside: 1. db2jcc.jar2. db2jcc_license_c.jar you download from IBM site: Derby does not currently provide a network JDBC driver, therefore you must download the IBM DB2 Universal Driver:http://www-106.ibm.com/developerworks/db2/downloads/jcc/ 3. derbytools.jar you get it from the http://incubator.apache.org/derby/derby_downloads.html. Just download derby, unzip, and there is the tool!!! 2º STEP: Create a derby.bat: set classpath=%the folder where you have the 3 jars% java -cp derby.jar;derbynet.jar;derbytools.jar;db2jcc.jar;db2jcc_license_c.jar -Dij.driver=com.ibm.db2.jcc.DB2Driver -Dij.user=system -Dij.password=manager -Dij.protocol=jdbc:derby:net://localhost:1527/ org.apache.derby.tools.ij pause This derby.bat goes in the same folder where you have the jars. 3ºSTEP run the derby.bat, and if everything is ok, you will get in your command line: ij To connect to the SystemDatabase, Geronimo must be running!!! just type: ij CONNECT 'jdbc:derby:net://localhost:1527/SystemDatabase';ij create table gente (nombre varchar(50));0 rows inserted/updated/deleted thats all!!! thanks!! KatiaAcepta el reto MSN Premium: Envía hasta 500 megas diarios de fotos desde Hotmail. Descárgalo y pruébalo 2 meses gratis.
