eclipselink - Migration from Hibernate to eclipse link as the JPA provider -


we planning migrate hibernate 4.0 eclipse link our jpa provider can let me know kind of effort involved has gone down path.

i keen because of multi-tenancy superior in eclipse link

late answer, believe question may relevant others , answer can more complicated seems.

i consider 100% standard jpa usage. there differences may crucial. e.g.:

  • hibernate, default, not cache. eclipselink, default, caches massively. have check documentation of boths how migrate caching.
  • hibernate can find (scan) classes in java se environment default, eclipselink doesn't this. both in ee environment specified.
  • there bugs in both providers, 100% jpa may hit regularly depending on complexity of mapping, whether , how use jpql, etc. examples our practice:
    • hibernate not produce correct sql deletes across joins like: delete dog d d.breed.name = 'collie' (link)
    • or rather exotic eclipselink's delete of entity @onetomany referencing non-@id property (link)
    • as example, although fixed, there problems java 8 streams on lazy lists in eclipselink because misused vector (extended 1 without maintaining superclass' protected fields' invariants).

considering how many bugs open in both projects (which expected) may bug cross-fire when try migrate , forth.

so wrap up:

  • mind jpa provider specifics jpa specification not, well, specific (there many unspecified behaviors left providers). implicit caching settings 1 example. need read jpa provider docs use proper properties provider, etc.
  • mind bugs. :-)

Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -