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.
In Sun Java(TM) Studio Enterprise 8 on creating CMP Entity Bean from Sybase (and other DataDirect drivers) JDBC Connection 'DataSource Class name' property of generated connection pool resource is empty. It cause connection resource registration failure.
Daria, which build of the IDE are you using?
Just tried on my build, and I do see a correct class name in the wizard. After creation, I verified in the properties, and I did see this classname: com.sun.sql.jdbcx.sybase.SybaseDataSource please attach a bitmap for each steps you are following, and give the build number. I need to verify if the "jdbcx" value I see if the correct one or not...
I was using the file wizards under the sn resources category (new file...) So maybe this is not what you are using... I guess you registered an unlocked driver to the IDE? how did you unlock it? Did Nam implemented the unlock mechanism in the IDE already? Can you attach the bitmap of the db explorer with this driver, as well as one database using it? Also, add the bitmaps of the properties sheet of these nodes... As you know, I do not have access to these $$$ and locked by default drivers, so I need these bitmaps to read all the properties you have...
I did the change for service registration of JseOpenConnection in Buzz code line and verifed from the debugger that it gets created properly. If daria is using JSE Buzz official build, then it still based on 3/17 NetBeans binaries and might still have class loading problem causing unlocking failure.
So could you upgrade your private environemt with the correct latest build and test? We cannot wait too long, if a fix is really needed.
From what sent by Mikhail Vaysman, this is not unlock or connection problem. The connection is fine. The reason for DataSource classname empty probably out-of-date info from the plugin's static driver info.
Nam, I sent you a new plugin module you can test in your environment. We could move this bug to P2 if this does not solve the issue so that we can work on it this week. Also, jdbcx is correct I think.
Should be fix now... Let us know and reopen as p2 asap if not... We do not have access to these drivers unlocked in nb :-)
Verified with Build 200504031800. I have verified the bug with 1 database (DB2) but was not able to test it with other databases because of locked drivers. Will do more checks in next build and close the bug then.