Reverse engineering in eclipse: minor issues

gregory.mostizky · **Joined:** Wed Mar 21, 2007 9:56 am **Posts:** 1

Hi,

Long time hibernate user, but today was the first time I needed to perform reverse engineering from JDBC using hibernate tools.

Couple of minor issues I encountered, not sure if it's worth opening JIRA over it:

1) IndexOutOfBounds exception is thrown with no explanation when trying to reverse engineer from JDBC tables, if no tables match the specified parameters in reveng configuration. As a first time user I tried all kinds of different things to solve this (including reinstalling hibernate tools). A simple clear error message would have prevented this.

2) No visible progress when reverse engineering large number of tables. Eclipse progress indicator is stuck at 50% when the reverse engineering process works. A working progress bar and/or simple console output regarding current table being scanned would be really really nice.

I am using hibernate tools 3.2.0beta8 on clean eclipse 3.2

Regards,
Gregory

max · **Posted:** Wed Mar 21, 2007 1:44 pm

1) stacktrace ?

2) it shows progress for me...note some db's will be slow in giving the initial response hence no movement.

Sixel · **Posted:** Thu Mar 22, 2007 8:52 am

max wrote:

2) it shows progress for me...note some db's will be slow in giving the initial response hence no movement.

Using

Code:

RDBMS: Oracle, version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0
JDBC driver: Oracle JDBC driver, version: 10.2.0.1.0
Hibernate Tools 3.2 beta8

I just mapped ~50 tables, using a wildcard :

Code:

<table-filter match-name="FOO.*" exclude="false"/>

The progress bar went straightaway to 50%, got stuck for approx. 45 seconds (message was "reading jdbc metadata"), and then the reveng suddenly completed.

Quite misleading the first times you carry out reveng, but after a couple of times you learn to wait ;)

That's a minor issue, that could be "solved" by setting a more detailed status message, something as simple as "reading jdbc metadata (this process may take some minutes)" would avoid first users worrying...

hth,
alexis

max · **Posted:** Thu Mar 22, 2007 10:00 am

could you try and do it again while you have the Progress View open and let me know if you see progress there ?

Sixel · **Posted:** Thu Mar 22, 2007 10:47 am

max wrote:

could you try and do it again while you have the Progress View open and let me know if you see progress there ?

Oops, sorry, I forgot to mention that what is described is what I could see in the progress view actually.

max · **Posted:** Thu Mar 22, 2007 12:13 pm

and there is no iteration of table names etc there ?

Sixel · **Posted:** Thu Mar 22, 2007 12:35 pm

max wrote:

and there is no iteration of table names etc there ?

I can't tell for sure, since it all happens in a blink, but after the ~45 seconds stuck at 50% with the metadata message, the progress bar reaches then 100% during a second ('Hibernate XML Mappings (.hbm.xml)'or something similar), and then the task is removed from the progress view.

hth,
alexis