[Bob Skinner]

Hi
I’ve looked at a bunch of RE problems here but haven’t seen this one:

I’m running MyEclipse 5.0.1 GA in Eclipse 3.2.

Database Explorer connects with an Oracle 8.1 db via the ojdbc14_g.jar driver.

Doing the reverse engineering on a db table in a Hibernate-enabled app produces an error message “Internal Error occurred while generating artifacts.”

Here’s the stack trace:

java.lang.NoClassDefFoundError: oracle/net/ns/NSProtocol
at oracle.jdbc.ttc7.TTC7Protocol.connect(TTC7Protocol.java:1762)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:215)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:371)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:551)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:351)
at org.hibernate.console.FakeDelegatingDriver.connect(FakeDelegatingDriver.java:23)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:72)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1877)
at com.genuitec.eclipse.hibernate.wizards.MEJDBCMetaDataConfiguration.readFromJDBC(MEJDBCMetaDataConfiguration.java:71)
at com.genuitec.eclipse.hibernate.wizards.GenerateArtifactsJob$6.execute(GenerateArtifactsJob.java:514)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:35)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:70)
at com.genuitec.eclipse.hibernate.wizards.GenerateArtifactsJob.buildConfiguration(GenerateArtifactsJob.java:509)
at com.genuitec.eclipse.hibernate.wizards.GenerateArtifactsJob.run(GenerateArtifactsJob.java:293)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Thanks.

Bob Skinner

[Bob Skinner]

Hi

Just got this to work. The only changes since the original post have been: deleting references to unused drivers (classes12.jar) from the db browser setup, deleting other drivers from the build path, closing everything in Eclipse, shutting down Eclipse, and bringing it back up.

Some forums I visited said that classes12 was buggy and could be replaced by drivers for later versions of Oracle.

Bob Skinner

[Haris Peco]

Bob,

classes12.jar is very old jdbc driver and it is for jdk <= 1.3.Howeer, all oracle jdbc drivers are buggy, newer have less bugs
Why you use ojdbc14_g.jar – it driver contents debug information (it will not help you a lot) and they are slower ?

Thank you for your feedback.Your information are very valuable.

Regards,
Peco

[Author]

Posts