This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 79501 - Cannot create Entity Class from remote database
Summary: Cannot create Entity Class from remote database
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Libor Kotouc
URL:
Keywords:
Depends on: 80629
Blocks:
  Show dependency tree
 
Reported: 2006-06-30 15:21 UTC by Martin Schovanek
Modified: 2006-08-03 16:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schovanek 2006-06-30 15:21:41 UTC
[#200606300200, jdk1.5.0, remote Glassfish b48, Derby]

to reproduce:
-------------
1) create a Web Project, as server use remote Glassfish
2) create a data source on the remote server
3) invoke 'New > Entity Calsses from Database' wizard
4) chose the remote server data source
5) connect the data source
ERROR: the Available Tables panel is empty.

I am using Derby Sample DB, 'app' user with default 'APP' schema.  But the
wizard creates DB Connection with 'Default Schema' which seems to be empty.
Connection with 'APP' schema works well.
Comment 1 Libor Kotouc 2006-07-19 15:56:09 UTC
There is simple solution - when connection dialog is shown the correct schema
must be chosen on the second tab.
The problem with this solution is that the users are not aware of the schema
selection and there is no explanation of it.

The best is to create new connection with the help of the user. It means not to
create it automatically as now but to show the common 'new connection' dialog
with known data prefilled. Current mechanism forces the user to select the
schema if no appropriate one is found.
Unfortunatelly the API provided by the db module is not sufficient - it does not
allow to pass all known db connection parameters. New API change request is
filed for this, see the issue 80629.
Comment 2 Libor Kotouc 2006-07-28 17:31:15 UTC
Fixed.

Checking in DatabaseTablesPanel.java;
/cvs/j2ee/persistence/src/org/netbeans/modules/j2ee/persistence/wizard/fromdb/Attic/DatabaseTablesPanel.java,v
 <--  DatabaseTablesPanel.java
new revision: 1.1.2.32; previous revision: 1.1.2.31
done
Comment 3 Martin Schovanek 2006-08-03 16:37:57 UTC
v.