Would it be possible to consider the following enhancements:

1.  At present, if you are trying to create a single entity for a single table, the current wizard attempts to list 
all tables in the schema.  With a very large database, eg. PeopleSoft CS8.9, the process of listing all of the tables 
can take over 30 minutes (at which point I simply closed the app - some no indication of the final time is 
available).  Can a filtering mechanism be introduced similar to Oracle's wizard in JDeveloper - the filtering 
mechanism would allow you to filter the query used to retrieve the list for a group of tables based on a pattern, 
hopefully improving retrieval time.  The inclusion of related tables would possible need to be reviewed to only query 
the database for related tables once the filtered items have been selected.  Alternately make this the users 
responsibility.

2. At present, you cannot create an entity for a table that does not contain a primary key.  However, there are cases 
where it would be useful to do this.  For example, PeopleSoft does not use the primary key mechanism, only the 
definition of an index related to the keys.  In this case it would still be very useful to jump start coding by having 
the entity created from the tables.  The user can then proceed to add additional annotations manually to the entities 
to define the virtual primary keys to be used.