5.3.3 Supported application formats

A J2EE application using the JPA is deployed on Application Server in one of the following formats:

You can also replace a J2EE application that uses a deployed JPA. For the archive format, use the redeploy functionality and for the exploded archive format, use the reload functionality.

Note that when you use the reload functionality, updates are not detected for the O/R mapping file. However, the O/R mapping file is re-read when the file is reloaded. The following table describes the targets for update detection and the re-reading during reload.

Table 5-3 Targets for update detection and re-reading when reload is executed

Target classes and filesUpdate detectionRe-reading
Entity classYY
Mapped super classYY
Embedded classYY
persistence.xmlYY
O/R mapping file
(When orm.xml is allocated under META-INF)
NY
O/R mapping file
(When orm.xml is allocated to the location specified in the <mapping-file> tag of persistence.xml)
YY
Legend:
Y: Target
N: Not a target

For details on the J2EE applications in the archive-format and the exploded archive-format, see 13. Formats and Deployment of J2EE Applications.

Note
When you use an application with the JPA in the exploded archive format, do not delete the class or library JAR while the application is running. If the class or library JAR is deleted, Application Server and JPA provider might perform unexpected operations.