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.
| Summary: | Can not create/use other/new persistence library | ||
|---|---|---|---|
| Product: | javaee | Reporter: | err <err> |
| Component: | Persistence | Assignee: | Sergey Petrov <sj-nb> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | pjiricka |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
err
2009-09-10 19:45:15 UTC
Forgot to mention that the persistence library I defined before doing this was already part of the project. it shouldn't be a big problem with m7 as from today nb is bundled with eclipselink 2.0 m7, but still may be an issue with addition of new libraries. Change summary to reflect the higher level issue (not just the specific issue with eclipselink) there are several points why it may not work, - nb show persistence library only if it know about this persistence library, - also nb show only one provider item in drop down per known provider versions and it have sense because from code sde without libraries there may be no way distinguish even eclipselink 1.0 and 2.0, and if we speak about milestones it's even more worst case. > there are several points why it may not work, > - nb show persistence library only if it know about this persistence library, "New Persistence Library..." and its dialog seems to check that the jars are valid since it has that "EntityManager is not present on library classpath" check. Doing this dialog, would notify NB about the new library for its list. > - also nb show only one provider item in drop down per known provider versions and it have sense because from > code sde without libraries there may be no way distinguish even eclipselink 1.0 and 2.0, > and if we speak about milestones it's even more worst case. In the "New Persistence Library..." dialog you give the library a name. So it would not be a problem to have all the milestone builds for example, each with a different name. Like: persistlib-M5 persistlib-M6 persistlib-M7 persistlib-release About the "Manage Libraries...", I guess if you pick a library there, then exit that dialog it should be validated with the "EntityManager is not present on library classpath" check. If there is no time to do this for 6.8, then "New Persistence Library..." "Manage Libraries..." should probably be taken out of the drop down combo box, and the 'define your own' feature dropped for 6.8. There is a potential problem that there might be a bug fix of eclipselink and no easy way to start using it without this feature. yes, library have name but in persistence unit dialog you have no selection for library, only for provider and library is determined based on provider, either there should be additional selection of library if multiple exist or providers list should extends and have smth like "EclipseLink (libname)" items. before removal or enhancment it's good to check if new dismiss last comment. I think I understand better now. Yes, it looks like the UI is missing some stuff to make use of multiple libraries of the same provider. *** Issue 173087 has been marked as a duplicate of this issue. *** looking into the issue once more. it may be possible to separate drop down items into items with some library match or have additional dialog or/and drop down. but it looks more like a corner case as we are trying to have ui simple and working in less clicks and providing correct result for most cases, usage of M3,M4,M5 etc looks like a corner case I see no usual for development. except milestones, there are mor valid use cases for support this feature, new versions with the same jpa version support may be releasd. without control for libraries, persistence nb support will use first in order, it may be the way to workaround the issue if change order in ant library list (with library name changes). Report from old NetBeans version. Due to code changes since it was reported likely not reproducible now. Feel free to reopen if happens in 8.0.2 or 8.1. |