{"id":99,"date":"2011-02-15T20:31:35","date_gmt":"2011-02-16T03:31:35","guid":{"rendered":"http:\/\/sloanseaman.com\/wordpress\/?p=99"},"modified":"2011-07-17T10:01:06","modified_gmt":"2011-07-17T17:01:06","slug":"websphere-hibernate-jpa-with-a-twish-of-classpath-hell","status":"publish","type":"post","link":"http:\/\/sloanseaman.com\/wordpress\/2011\/02\/15\/websphere-hibernate-jpa-with-a-twish-of-classpath-hell\/","title":{"rendered":"Websphere, Hibernate, JPA, with a twist of Classpath hell"},"content":{"rendered":"

Problem<\/h3>\n

Recently I had to take a .war project that utilized Hibernate 3.5 and JPA 2.0 and deploy it in WebSphere 7.0. It has been quite a long time since I worked with WebSphere and was very happy to find that it was very easy to setup and deploy my existing war.<\/p>\n

What I didn’t expect was the Classpath mess that was to ensue and the 7 hours of research to find a solution to what appears to be a fairly common problem (but no real solution defined)<\/p>\n

You see, WebSphere ships with a copy of OpenJPA. OpenJPA is a JPA implementation that WebSphere provides for use by developers. It just so happens though that the OpenJPA that WebSphere ships with is a JPA 1.0 implementation. <\/p>\n

Hibernate 3.5 or > requires a JPA 2.0 implementation. Houston, we have a problem.<\/p>\n

No problem you think. I’ve got the JPA 2.0 implementation (hibernate-jpa-2.0-api01.0.0.Final.jar) in my .war’s classpath, so I’m fine. Right?<\/p>\n

Wrong. WebSphere puts OpenJPA on the Classpath first, no matter what. You can change the configurations (Parent first\/Parent last) and it will still have OpenJPA on the Classpath before the .war file. You’ll start seeing a lot of weird errors like:
\njava.lang.NoSuchMethodError: javax\/persistence\/spi\/PersistenceUnitInfo.xxxx<\/code><\/p>\n

If you see the above you have a JPA 1.0\/JPA 2.0 issue because of OpenJPA. <\/p>\n

Solution<\/h3>\n

IBM has a Feature Pack (think library upgrade package) for WebSphere to get it to run OSGi and JPA 2.0. Once you install this everything should work fine.<\/p>\n

Steps:<\/p>\n

    \n
  1. Shutdown WebSphere<\/li>\n
  2. Download the IBM Install Manager at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24027833<\/a> if you don’t already have it.<\/li>\n
  3. Start the IBM Installation Manager\n
      \n
    1. Make the Install Manager aware of your WebSphere installation if it isn’t already\n
        \n
      1. Select IMPORT from the main page<\/li>\n
      2. Select the installation directory of your copy of WebSphere<\/li>\n
      3. Select next for the rest of the steps until finished<\/li>\n<\/ol>\n<\/li>\n
      4. Back at the main IBM Installation Manager screen select INSTALL\n
          \n
        1. Select the Feature Pack for OSGi Applications and JPA 2.0<\/li>\n
        2. Install the Feature Pack<\/li>\n<\/ol>\n<\/li>\n
        3. Once done, exit the IBM Installation Manager<\/li>\n<\/ol>\n<\/li>\n
        4. Start the IBM Profile Manager\n
            \n
          1. In the Profile Manager, Select the Server then click AUGMENT<\/li>\n
          2. Select the JPA 2.0 and click NEXT then click INSTALL<\/li>\n
          3. Exit the IBM Profile Manager<\/li>\n<\/ol>\n<\/li>\n
          4. Start up WebSphere\n
              \n
            1. To Verify that the install took:\n
                \n
              1. Go to the web interface for the WebSphere server<\/li>\n
              2. Select SERVERS -> SERVER TYPE -> WEBSPHERE APPLICATION SERVERS -> SERVER1 -> RUNTIME -> PRODUCT INFORMATION<\/li>\n
              3. You should see ‘Feature Pack for OSGi Applications and Java Persistence API 2.0’<\/li>\n<\/ol>\n<\/li>\n
              4. Uninstall your .war, .ear, .etc and reinstall it<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

                The errors should disappear and everything should start working!<\/p>\n

                Things to note<\/h3>\n