Components must be archived as part of the package where they are installed. You can archive in two formats:
EAServer JAR This format, while proprietary to EAServer, supports all component types. Also, unlike the EJB-JAR format, all component property settings are preserved in the archive.
EJB JAR This format provides portability between J2EE and EJB servers from different vendors. Only EJB components are archived in this format; components of other types are ignored when you create the archive. Not all component properties are preserved in the archive, because the deployment descriptor does not support all EAServer properties. These EAServer properties can be configured by including an EAServer XML configuration file in the archive, as described in “Using EAServer configuration files in J2EE archives”. The following settings in the Component Properties dialog box are not configured by the EJB-JAR deployment descriptor, and must be configured in the XML configuration file or manually after deployment:
For beans that use container-managed persistence, the Persistence settings.
Role mappings and method-level permissions.
Resource references.
EJB references to components that are not installed with the JAR file or when multiple beans use the same home and remote interfaces. It is impossible to infer EJB references if more than one bean uses the home and remote interfaces specified by the reference properties in the deployment descriptor. After importing an EJB-JAR file that contains multiple beans that use the same home and remote interfaces, view the EJB Reference properties to verify that the correct bean is invoked.
Environment properties.
For EJB 2.0 components, Resource Environment Refs properties.
For EJB 2.0 components, Run As Identity properties.
For information on these properties, see the EAServer Manager online help or the EAServer Programmer’s Guide.
EJB 1.0 JAR This format supported for backward compatibility. It is similar to the EJB-JAR format, but supports only EJB version 1.0 components. For more information on this format, see Appendix A, “Using EJB 1.0 JAR Support.”
