Wednesday, March 10, 2010

Why I haven’t tried JPA?

Tagged with: , ,
Monday, January 7, 2008, 2:03
This news item was posted in Notes category and has 7 Comments so far.

I have been implementing java for 4 years and what I have learned: “not all Java API’s are good” but there are some open/vendor APIs you should prefer.

I have developed EJB 2.1 with JBoss but it is always a vendor dependent implementation and never, even for once tested on any other application server. And its the only way you can do this, with a medium or small size project. Moreover it has very slow learning curve and very limited development support.

I have also tried JDO ,java’s first attempt against hibernate,second attempt to persist java. JDO 1.0-1.1 is very magnificent API, very radical way. Post-Compile time enhancement: brilliant!!!. but when it comes to runtime its query language is not as strong as SQL. And JDO was not allowing DB mapping. And again it was a failure

Same year I used javax.portlet 1.0 on IBM. In brief: think about an API that has lots of lack. to fix this you should use IBM API and taglib. Again a heterogeneous solution: again a failure.

And org.hibernate against many more APIs/framework it is still standing why? quicker response times , huge community support just one vendor support.

As a solution I currently prefer proven standards :

some of them open source frameworks: struts2, hibernate, spring,acegi

Share and Enjoy:
  • Digg
  • del.icio.us
  • Netvouz
  • DZone
  • Wists
  • LinkedIn
  • Slashdot
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • email
  • Twitter

Related posts:

  1. hibernate native Id generator tip
  2. Why ORM? ’cause:
  3. Runtime Java Stack

You can leave a response, or trackback from your own site.

7 Responses to “Why I haven’t tried JPA?”

  1. Stephan Schmidt said on Monday, January 7, 2008, 3:34

    Hi, could you explain how Hibernate3 differs from JPA?

    Peace
    -stephan

    –
    Stephan Schmidt :: stephan@reposita.org
    Reposita Open Source – Monitor your software development
    http://www.reposita.org
    Blog at http://stephan.reposita.org – No signal. No noise.

  2. altuure said on Monday, January 7, 2008, 4:49

    Hi, JPA is just a subset of hibernate

    JPA do not support with no vendor support.
    caching,logging,interceptor

    to support these you have to use some vendor API
    eg:
    http://tapestryofthoughts.blogspot.com/2007/05/glassfish-and-audit-logging.html

  3. Stephan Schmidt said on Monday, January 7, 2008, 5:42

    The link you’ve supplied seems to concern TopLink, how does that concern Hibernate and JPA?

    Peace
    -stephan

  4. altuure said on Monday, January 7, 2008, 5:58

    I posted the link to show there is no solution in JPA for audit logging.
    Author show its solution with toplink API

  5. Tug said on Monday, January 7, 2008, 10:07

    The link that Altuure mentioned talk about Toplink because Toplink is the Reference Implementation of JPA, so part of the JavaEE RI: Glassfish.

    Altuure, base on the fac that JPA allows you to take advantage of its implementation layer using the Delegate API, why not trying to push a JPA usage to be “standard” and use the “hibernate” part only when needed. To take advance of a “real” standard instead of what could be called a defacto standard. And put yourself with a richer resume?
    I think that JPA has been a great effort in term of standardization and adoption of principle really pushed by user experience (instead of simple having a pure R&D approach).

  6. altuure said on Monday, January 7, 2008, 13:51

    In Fact I totally agree with you. But In a production environment you can skip some basic feature like caching and querying.
    Yes it is really good to work with different frameworks but it is also very risky to mix them unnecessarily.
    JPA may be an industry standard for some day but for now it is immature and a subset of open standards JPA/TopLink

    Thanks.

  7. hohonuuli said on Tuesday, January 8, 2008, 0:53

    I’ve been using JPA with some new projects. I’ve been VERY happy with it; I’m looking forward to it’s continued evolution and development.

Leave a Reply