Topic
6 replies Latest Post - ‏2009-12-22T13:00:41Z by sutter
millerkc
millerkc
3 Posts
ACCEPTED ANSWER

Pinned topic Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

‏2009-10-29T18:02:09Z |

Release notes: IBM WebSphere Application Server Version 7 Java™ Persistence API (JPA)2.0 Open Alpha

This thread contains important details about using the IBM WebSphere V7 Java Persistence API (JPA) 2.0 Open Alpha, including known problems and restrictions that may not be included in the documentation. This thread will be updated as new issues are discovered and documented.

Do not use the IBM WebSphere Application Server Version 7 Java Persistence API (JPA) 2.0 open alpha release for performance evaluations or for publishing performance benchmark results. The alpha release has not gone through the complete performance quality checks, which include aggressive production environment stress tests.

For platform support, please refer to the Getting Started Guide

OpenJPA release notes

IBM WebSphere Application Server Version 7 JPA 2.0 Open Alpha is based on OpenJPA 2.0 Milestone 3. Many known issues in this OpenJPA release are documented in the OpenJPA 2.0-M3 release notes

- WebSphere Application Server must be at version 7.0.0.5
- JPA 2.0 thin client JAR file must be first in the class path
- Bean Validation supported in Java SE only
- Annotation Processor tool and metamodel generation
- No support for delimited identifiers
- Profile Management Tool will not start after installing the IBM WebSphere Application Server V7 JPA 2.0 Open Alpha
- Embedded objects with CLOB fields cause errors with Derby 10.3.3.1 and later
- Cache data statistics may be inaccurate when using embeddables
- L2 cache configuration limitations
- @OrderColumn(updatable=false) does not prevent the UPDATE of order column



WebSphere Application Server must be at version 7.0.0.5

IBM WebSphere Application Server Version 7 JPA 2.0 Open Alpha requires you to have installed WebSphere Application Server Version 7 with fix pack 5. Higher and lower versions and fix pack levels are not supported. Fix pack 5 can be found here

 
JPA 2.0 thin client JAR file must be first in the class path

For thin client applications to use JPA 2.0, the JPA 2.0 thin client JAR file (com.ibm.ws.jpa.thinclient_7.0.0.jar) must be the first entry in the client application's class path

 
Bean Validation supported in Java SE only

Bean Validation support will not work inside a WebSphere Application Server container. It is currently only supported in Java SE applications.

 
Annotation Processor tool and metamodel generation

Compiling your source code with Java SDK 6.0 or later with the -processor option will generate the canonical metamodel. For example, the following command:


javac -processor org.apache.openjpa.persistence.meta.AnnotationProcessor6 --Aout=./generated org.acme.Foo


will generate source code for the canonical metamodel class for org.acme.Foo at generated/org/acme/Foo_.java. The only requirement is that the compiler invocation classpath must include the JPA and OpenJPA libraries."
 
Delimited Identifiers are not supported

There is no support for delimited identifiers in this release.

 
Profile Management Tool may not start after installing the IBM WebSphere Application Server V7 JPA 2.0 Open Alpha

After installing the IBM WebSphere Application Server Version 7 JPA 2.0 open alpha, the Profile Management Tool (PMT), which is located in the <WAS_HOME>/bin/ProfileManagement/ directory, may not start. If this occurs you will see a PMT dialog box that indicates that an error has occurred. There are two ways to work around this problem.

1) Instead of using the Profile Management Tool to create one or more profiles, you can use the manageprofiles command. See the WebSphere Application Server V7 Information Center for more information on the manageprofiles command.

2) Move three files that were backed up during the installation process out of the <WAS_HOME>/plugins directory. If you decide to move the files, you must move the files from your temporary location back to the <WAS_HOME>/plugins directory before you uninstall the IBM WebSphere Application Server V7 JPA 2.0 Open Alpha as specified in the Uninstalling the IBM WebSphere Application Server Version 7 JPA 2.0 open alpha section of the Getting Started Guide. The recommend steps to move the three files are:
  • Create a directory under <WAS_HOME> called jpabackup.
  • Move the following files from <WAS_HOME>/plugins to <WAS_HOME>/jpabackup.
    • com.ibm.ws.jpa.jar.JPA20
    • javax.j2ee.persistence.jar.JPA20
    • com.ibm.ws.runtime.jar.JPA20

 
Embedded objects with CLOB fields cause errors with Derby 10.3.3.1 and later

When using an Embedded object that contains a CLOB field to access a Derby database table and using the Derby JDBC Network Client Driver, you may encounter this error:


org.apache.openjpa.persistence.PersistenceException: You cannot invoke other java.sql.Clob/java.sql.Blob methods after calling the free() method or after the Blob/Clob
's transaction has been committed or rolled back.


This problem occurs with Derby versions 10.3.3.1 through 10.5.*.

If Embedded CLOB support is being used, possible workarounds are to use the Derby Embedded JDBC driver with these releases of Derby, or use an earlier release of Derby.

 
Cache data statistics may be inaccurate when using embeddables

When using entities with embeddables, the level 2 cache statistics may not be correct.
 
L2 cache configuration limitations

The cache retrieve mode and cache store mode properties may only be specified on the Persistence Unit or Persistence Context level. Setting the cache mode properties on the EntityManager.find(), EntityManager.refresh(), or Query.setHint() operations is not supported.

 
@OrderColumn(updatable=false) does not prevent the UPDATE of order column

If you have an existing collection with two items, then you remove an item and then add the item back in, the table is updated but the order column is not updated. If you add a third item, the new item is inserted into the collection.
Updated on 2009-12-22T13:00:41Z at 2009-12-22T13:00:41Z by sutter
  • kfokuo
    kfokuo
    4 Posts
    ACCEPTED ANSWER

    Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

    ‏2009-12-18T16:58:20Z  in response to millerkc
    Will IBM provide support for the Alpha version in production?

    We are really interested in using some of the new features in JPA 2.0 such

    as the Criteria searching.

    Which version of JPA does WAS 7.0.5 support out of the box?
    • sutter
      sutter
      94 Posts
      ACCEPTED ANSWER

      Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

      ‏2009-12-21T14:24:56Z  in response to kfokuo
      Hi kfokuo,
      I'm sorry, but the JPA 2.0 Open Alpha will not be supported in production. The idea of the early Alpha driver is to generate interest and to allow early experimentation of the new technology. We still have some additional testing that needs to be performed before it will ready for production use.

      I'm glad to hear of your interest in the Criteria API. This is definitely one of the highlights of the JPA 2.0 release. You are certainly encouraged to try out the Criteria API feature as delivered in the Alpha and provide any type of feedback. Thanks.

      WAS v7.0.5 delivers the JPA 1.0 level of function. Specifically, the WebSphere JPA solution in WAS v7.0.x is built on top of the Apache OpenJPA 1.2.x service branch.

      Hope this information helps,
      Kevin
      • kfokuo
        kfokuo
        4 Posts
        ACCEPTED ANSWER

        Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

        ‏2009-12-21T17:49:11Z  in response to sutter
        OpenJPA 1.0 is very very old. Many companies are embracing EJB3 on WebSphere 7.

        For us not to have a way of using OpenJPA 2 in a production environment with WebSphere

        7 is very very disappointing.

        Why can't IBM provide support for the alpha version in production and provide a fix for any

        issues and then ensure fixes are rolled out in production version.

        If you aren't going to provide support how are fixes handled for Alpha version?

        If I download and submit PMR on issue will IBM fix it and provide me with a patch?
        • sutter
          sutter
          94 Posts
          ACCEPTED ANSWER

          Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

          ‏2009-12-21T18:36:11Z  in response to kfokuo
          Hi,
          I think you are confusing the JPA 1.0 specification with Apache OpenJPA 1.0, the implementation. You are correct, OpenJPA 1.0 is "old", but it continues to be updated. The EJB3 Feature Pack for WebSphere v6.1 is based on the Apache OpenJPA 1.0.x service stream. This service stream is updated as customers discover issues (PMRs) in that environment.

          The JPA solution in WebSphere v7.0 is based on the Apache OpenJPA 1.2.x service stream. Yes, the specification behind this is still JPA 1.0. But, this service stream is continually updated with fixes (and features) for customer discovered issues (PMRs). Performance improvements are also included in this service stream, if they can be introduced without disrupting current usage.

          The JPA 2.0 specification just became final on Dec 10, 2009 (only 11 days ago). My apologies for not having a production ready implementation of this specification ready for WAS v7 just yet... :-) The Open Alpha was based off of the last public version of the specification (2nd proposed final draft). Our next goal is to ready an OpenJPA driver that is JPA 2.0 spec compliant and passes the TCK (also just made available on Dec 10, 2009).

          As stated previously, it's IBM's policy to not discuss release dates via these forums. Thus, I can not respond to when or how a production-ready version of the WebSphere JPA 2.0 solution will be ready for your consumption. Until that time, support will be provided via this forum. Updating the download site with newer versions of the Open Alpha code will be based on the need of the customers using the Alpha and how this matches up with the other release goals.

          Again, Thank You for your interest in our JPA 2.0 solution. I really encourage you to try out the features that you are interested in and provide feedback via the forum. Thanks.

          Kevin
          • kfokuo
            kfokuo
            4 Posts
            ACCEPTED ANSWER

            Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

            ‏2009-12-22T04:57:17Z  in response to sutter
            Ok,

            We have a big need for OpenJPA 2 for a new project. Please add us to the list of clients who have a big need for it.

            Is OpenJPA 2 compatible with Seam 2.2.0?
            • sutter
              sutter
              94 Posts
              ACCEPTED ANSWER

              Re: Release notes: IBM WebSphere Application Server V7 JPA 2.0 open alpha

              ‏2009-12-22T13:00:41Z  in response to kfokuo
              Excellent! We're glad to hear of your interest in WebSphere's support of JPA 2.0.

              There should be no problem using Seam 2.2 with WebSphere's JPA 2.0 implementation. Seam is supposed to work with any JPA implementation, not just Hibernate. And, since JPA 2.0 is backwards compatible with JPA 1.0, Seam should continue to work as it has in the past.

              Kevin