Known problems and limitations for JPA applications

Various known problems and limitations apply when you are working with WebSphere® Developer Tools. Issues include, among others, null pointer exceptions when you create entities from the JPA Manager Bean Wizard or Configure Entities Wizard.

Limitation when you create entities from the JPA Manager Bean Wizard or Configure Entities Wizard

When a user attempts to create Entities from the JPA Manager Bean Wizard or Configure Entities Wizard for a project that doesn't have the JPA facet installed, you can receive a null pointer exception.

You can work around the problem with the following steps:
  1. Open project Properties.
  2. Go to Project Facets.
  3. Check JPA facet.
  4. Click OK.

Projects that are required by web fragment projects are not automatically added to the Java build path

Projects that are required by web fragment projects are not automatically added to the Java build path.

If you have a web application project that contains one or more web fragment projects, and the web application project has references in its deployment assembly page to projects that are required by the web fragment projects, then those dependent projects (such as the JPA and Utility projects) are not automatically added to the Java build path of the web fragment projects.

You can work around this problem. Manually add the dependent projects to the Java build path of the web fragment projects in order for them to compile.

Java EE batch jobs logs view does not always show the log for the submitted job

[8.5.5.6 or later]If the Liberty server uses Java batch memory-based persistence, and you submit a job with WebSphere Developer Tools, then the Java EE batch jobs logs view does not show the log for the submitted job. In the progress view, a job with the status Processing Java EE Batch job log entries shows, but it never finishes.

Icon that indicates the type of topic Reference topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: r_limitations_jpa.html