Generating artifacts error MyEclipse5.1 generated mapping file

Using Eclipse3.2.1+myeclipse5.1+classes12.jar+hibernate3

Built a Hibernate3 Project, using the Classes12.jar driver above, in MyEclipse DB Browser

Connect to the database, select the table, click Hibernate Reverse engnieering in the context menu, directly click the Finish button,

There was an error generating the mapping file:

An internal error occurred during "generating artifacts"

Originally in Eclipse3.1+4.1+hibernate connection DB2 all normal, once with MyEclipse5.0 also normal generation mapping file, can recently always connect oralce generate mapping file when the above error, has not been to find what reason, shelved for a long time, I'd like to see MyEclipse. What is the mapping file of a one-to-many relationship generated by a table with a primary foreign key relationship (where the child table has its own primary key), and find out what's going on online?

Online talk is basically said to drive too old, must replace the updated driver, because I installed the Oracle92, so for MyEclipse designated ORACLE92 installation directory driver, the following package 1, 4, 9, 10 are Yiyi tried, but the fault is still

1.  %orahome%\jdbc\lib\classes111.jar
2.  %orahome%

\jdbc\lib\classes111.zip
3.  %orahome%

\jdbc\lib\classes111_g.jar
4.  %orahome%

\jdbc\lib\classes111_g.zip
5.  %orahome%

\jdbc\lib\classes12.jar
6.  %orahome%\jdbc\lib\classes12.zip
7.  

%orahome%\jdbc\lib\classes12_g.jar
8.  %orahome%

\jdbc\lib\classes12_g.zip
9.  %orahome%\jdbc\lib\ojdbc14.jar
 

%orahome%\jdbc\lib\ojdbc14_g.jar
%orahome% \jdbc\lib\classes12dms.jar.


%orahome%

\jdbc\lib\classes12dms_g.jar

By chance, after Eclipse restarts, the same method is used to generate the mapping file successfully, look at the reboot configured before the Oralce driver is used on the 10th package.

It is also smooth to use the problematic Oracle driver Classes111.jar not to restart Eclipse to generate the mapping file, so be sure to remember to use the new driver to generate the image after reconfiguring the MyEclipse Database Explorer driver Restart your Eclipse before shooting the file, although it is possible to immediately use the driver you just configured when you connect, but it's a bit stubborn to generate the mapping file, which is probably a Bug in MyEclipse.

It should be possible to use any of the drivers listed above, with only a different focus, and not knowing which of the previous Classese111.jar came to haunt me for so long.

Read the online introduction that Oracle is more recommended by the Ojdbc12.jar drive.