Notices tagged with eclipselink
-
Ah, the link didn't make it in: http://stackoverflow.com/questions/2243730/jpa-hibernate-embedded-and-enum
It is about #Hibernate and I use #EclipseLink here but still the enumeration can be used in #JPA to persist DayOfWeek "compatible" stamps.
-
The class does not have a descriptor, or a descriptor that does not use inheritance or uses a ClassExtractor for inheritance
The mentioned message still comes when you have @Inheritance (strategy = InheritanceType.TABLE_PER_CLASS) in your abstract (not-persisted) with latest version of #Payara / #Glassfish which both contains #EclipseLink by default.
Strange that they did not yet fix it. And unfortunally migrating to e.g. #WilfFly (which uses other #JPA) seems not so easy as you may think.
Currently I have no idea how to fix it and sadly I need the strategy as this #JavaEE application is written for an existing database layout.
Someone may have to raise a support ticket mentioning that the #bug is still there.
Reposted with #public visibility. Sorry for double message.
-
So I have here a relative complex #Entities structure: User -> Contact and Contact -> CellphoneNumber, LandLineNumber, FaxNumber this means that Contact is referencing 3 other entities. If I run #persist on User, all went fine with #EclipseLink, but If I run a #merge() on User, the 3 last entities got persisted (inserted instead of updated) again and in Contact the constrains are being updated to the new ones. So I have some orphaned entries to remove (which causes another SQL). cc !java ...
-
@netmackan well, since #Payara is based on #Glassfish, I guess I will face the same problems when I try to use #Hibernate (as it does an UPDATE and not as #EclipseLink does an INSERT on updating referenced entities).
-
For the last 3 (!) days (including today) I tried to fix the problem that while the #JPA is merging (similar to UPDATE #SQL statement) entities, some tables got filled with new rows (search for "eclipselink insert instead update") which leaves orphaned rows behind. I could enable orphanRemoval=true but that only adds another performance penalty. So I decided to switch to #Hibernate instead of remaining with #EclipseLink. cc !java