Changing or adding EJB JAR files
You can change enterprise bean (EJB) Java™ archive (JAR) files on application servers without having to stop the server and start it again.
About this task
However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.
The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions.
There are several changes that you can make to EJB JAR files without stopping the server and starting it again.
The following table lists the changes that you can make to EJB JAR files by manipulating an EJB file on the server where the application is deployed. The table also states whether you use hot deployment or dynamic reloading to make the changes.
Change | Hot deployment | Dynamic reloading |
---|---|---|
Change the ejb-jar.xml file of an EJB JAR file. | Not applicable | Yes |
Change the ibm-ejb-jar-ext.xmi or ibm-ejb-jar-bnd.xmi file of an EJB JAR file. | Not applicable | Yes |
Change the Table.ddl file for an EJB JAR file. | Not applicable | Not applicable |
Change the Map.mapxmi or Schema.dbxmi file for an EJB JAR file. | Not applicable | Yes |
Update the implementation class for an EJB file or a dependent class of the implementation class for an EJB file. | Not applicable | Yes |
Update the Home/Remote interface class for an EJB file. | Not applicable | Yes |
Add a new EJB file to an existing EJB JAR file. | Yes | Yes |