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.
Build: NetBeans IDE 6.9.1 (Build 201007282301) VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02 OS: Windows XP User Comments: dan.deter: Using the Hibernate Reverse Engineering Wizard to create the reveng.xml file from an oracle database. GUEST: I'm trying to configure the reverse engineering tool GUEST: Conecction with the Oracle DataBase 10g r2 Stacktrace: java.lang.UnsatisfiedLinkError: Native Library C:\Oracle\ora10204\BIN\ocijdbc10.dll already loaded in another classloader at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1768) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1728) at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:4085) at java.security.AccessController.doPrivileged(AccessController.java:0)
Created attachment 101833 [details] stacktrace
The workaround i found is to use the oracle thin driver in the 'hibernate configuration wizard' I don't know if this will cause some side effects in the next development steps. To use the oracle thin driver I selected: 1- New Hibernate Configuration Wizard; 2- In the Database connection field select: New Database Connection; 3- the New Database Connection window will be shown; 4- In the driver name I selected: New Driver; 5- the New JDBC Driver dialog will be shown; 6- click the add button and select the ojdbc6.jar which is in the folder: <oracle_path>\oracle\product\11.1.0\client_1\jdbc\lib 7- automatically the fields Driver Class and name will be filled with Oracle Thin; 8- use this JDBC Driver for the hibernate configuration.
may be fixed with issue 194449 if classloader will be properly released after usage (but may not if it will be loaded by one classloader in services tab and second hibernate classloader). it's good there is a workaround.
mark as works for me as it's unclear if it was fixed, but according to latest comment it may be fixed as side effect of another issue and there are no reports after 6.9.1