I see the eclipselink JPA provider has been added last week to Nb 6.1 (http://hg.netbeans.org/main/rev/0e761d4c329c) but
this is incomplete to be functional for GF V3 (or others).
It seems that there is still missing code to make it available like kodo or openjpa are.
See code for example under:
addPersistenceProvider(ProviderUtil.HIBERNATE_PROVIDER, "hibernatePersistenceProviderIsDefault", platform,
result); // NOI18N
addPersistenceProvider(ProviderUtil.TOPLINK_PROVIDER, "toplinkPersistenceProviderIsDefault", platform,
addPersistenceProvider(ProviderUtil.KODO_PROVIDER, "kodoPersistenceProviderIsDefault", platform, result); // NOI18N
addPersistenceProvider(ProviderUtil.OPENJPA_PROVIDER, "openJpaPersistenceProviderIsDefault", platform, result);
but nothing for EclipseLink
Also, trying to add a new persistence library, even if I add the eclipselink libraries, I still get
a red error with "EntityManager is not present on library" message.
So so far, I am not able to register eclipselink or register it...
P3: If I add the JPA apis in the library definition I can create the lib, so it seems that EclipseLink does not include
the api jar.
Still P3 for the webproject (and possibly other project types) lack of exposure with EclipseLink.
EclipseLink includes the API jar in a separate library which you of course need to add to the library. As for detecting
the EclipseLink as the default provider in GF V3, that is an enhancement.
trunk fix is http://hg.netbeans.org/main/rev/8d9f40c0a920
Nominating for NB 6.1 Patch 2. It is needed by the GlassFish V3 JavaEE Integration plugin for correct display of
EclipseLink JPA support.
So, ludo, this is fixed? If yes, please mark it as FIXED.
The patches are intended for defect bugfixing only but not for an enhancement implementation. If this issue is a real
enhancement, please remove it from the patch. If it is a defect, please change the issue type. Thanks.
Please clarify if this issue is fixed or not (it has still status NEW).
The diff shows just one line added, so I suppose it is a fix (not an enhancement).
If it should go into patch 2, then we need verification from QA.
fix in trunk
assigning tot dongmeic for the branching work
f in trunk
The fix needs to be verified by QA. QA, can you verify it till 10-Jun-2008?
Then it will be ported by sustaining to patch 2...
This issue has been nominated for NB IDE 6.1 patch2 although it hasn't been verified by QE yet. If it isn't verified by
12-Jun-08, it's nomination will be removed.
Verified in the latest trunk build.
the only way to verify it is to use the GF V3 plugin from the contrib source code.
Create a web app with this server target, and create JPAs from DB. You should see the EclipseLink provider as the
default for it.
I've verified the behaviour.
The change has no effect for all the other server plugins
The fix has been ported into the release61_fixes repository.