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.

Bug 170311

Summary:	JDBC driver deployment does not work
Product:	serverplugins	Reporter:	Petr Jiricka <pjiricka>
Component:	Tomcat	Assignee:	Petr Hejl <phejl>
Status:	NEW ---
Severity:	blocker	CC:	emononen, manikantannaren, sj-nb
Priority:	P2
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Petr Jiricka 2009-08-13 10:52:49 UTC

1. Create a new web application with Tomcat 6 as the target server
2. Register a db connection (for example by registering GlassFish v3, which registers the Derby sample)
3. Create JPA classes from database (e.g. using the sample database), using EclipseLink as the persistence provider
4. Deploy the application

=> I expect that the Derby JDBC driver (derbyclient.jar) will be copies to the Tomcat lib directory, but nothing is copied.

Comment 1 Petr Hejl 2009-08-14 12:45:38 UTC

This seems to be related to used container. The wizard behaves differently when there is a container managed persistence
provider. The tomcat does not have one so it is more similar to j2se - connection is configured directly in
persistence.xml and there is no datasource (and no datasource to deploy).

It works this way in 6.5 and 6.7, so perhaps this is an enhancement to cover a missing use-case for tomcat. This will
possibly need some API extension.

Comment 2 Petr Jiricka 2009-08-14 13:26:21 UTC

In that case I agree this is an enhancement, cc'ing Sergey.

Comment 3 manikantannaren 2014-02-12 03:21:32 UTC

Does not work with Glassfish either
Tutorial
https://netbeans.org/kb/docs/web/hibernate-webapp.html

go to the trouble shooting step.

I have enabled  "Enable JDBC Driver Deployment option is selected for your GlassFish server."
But still I had to manually copy the MYSQL connector jar to the glassfish domain/lib folder.