8.3.3 Supported application formats
A J2EE application using the JPA is deployed on Application Server in one of the following formats:
-
Archive-format J2EE applications
-
Exploded-archive format J2EE applications
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.
|
Target classes and files |
Update detection |
Re-reading |
|---|---|---|
|
Entity class |
Y |
Y |
|
Mapped super class |
Y |
Y |
|
Embedded class |
Y |
Y |
|
persistence.xml |
Y |
Y |
|
O/R mapping file (When orm.xml is allocated under META-INF) |
N |
Y |
|
O/R mapping file (When orm.xml is allocated to the location specified in the <mapping-file> tag of persistence.xml) |
Y |
Y |
- Legend:
-
Y: Target
N: Not a target
For details on archive-format J2EE applications and exploded archive-format J2EE applications, see the manual uCosminexus Application Server Common Container Functionality Guide.
- Important 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.