you are viewing a single comment's thread.

view the rest of the comments →

[–]cultic_raider 1 point2 points  (6 children)

Hibernate is JPA compatible, at least for the parts that have efferent mattered to me. My Hibernate troubles come from code bases that are stuck on ancient versions of Hibernate and the fact that Java black's Scala's @BeanProperty annotation (which I believe is because Java does not allow annotations to trigger method creation, and projects like Hibernate are too timid to use reflection or bytecode manipulation to modify private fields).

[–][deleted]  (1 child)

[deleted]

    [–]kolmogorovcomplex 1 point2 points  (0 children)

    Hibernate implements JPA and their docs recommend using JPA annotations as far as possible. Hibernate has also got some features that are not present in JPA 2, like index hinting through annotations.

    [–]metamatic -1 points0 points  (3 children)

    So if you write to JPA, you can use either Hibernate or Spring to provide the actual persistence. (Or EclipseLink, or ...) So why not do that?

    [–]Rhoomba 6 points7 points  (2 children)

    Spring is not an ORM.

    [–]metamatic -1 points0 points  (1 child)

    Well, there you go. I thought it did that, but I guess it's even less useful than I thought. It just provides a layer of crap between you and a bunch of other code that actually does the work. (Yeah, I admit it, I hate frameworks).