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.
I saw this problem when testing a web app with tomcat/hibernate. The web app is 2.4 so it uses jdbc instead of data source. The PU wizard forces you to create a library with hibernate ejb 3 entity manager to let you create a PU. But in reality you do not need this library because the server already has it. Also, you must not deploy the library with the web module otherwise jboss classloaders will be confused. So I think that the PU wizard should detect if you already have a EM provider in project cp (such as from server, but even otherwise) and have an option <No Library - use provider from project> (maybe better wording... Erno, Martine, what do you think?
I will do it for 5.5 is you see no problem with this.
I think this is a good idea. Maybe provider's name could be displayed for this option also as there might be more than one provider in classpath.
Issue 80421 should be resolved before this can be implemented, now it is not possible to detect what persistence providers are already on the server.
Setting the TM to future for now as issue 80421 needs to be fixed first (which likely won't happen before 6.0 since it was not accepted as a defect).
As for the particular issue describe in this issue, it does not exist any more (must have been fixed in 6.0). The user does not required to have the persistence lib in the project before creating any PU. Mark it as fixed in 6.5 since I just verified in NB 6.5.
verified. NetBeans IDE Dev (Build 200812080201)