Define WebSphere Extension properties for your EJB

You can to define WebSphere® Extension properties for your Enterprise Java™ Beans.

Procedure

  1. In the Enterprise Explorer view, right-click the EJB project that includes the entity bean for which you want to define WebSphere Extension properties.
  2. Right click the deployment descriptor, and select Open With > Deployment Descriptor Editor.
  3. Select the bean on the Bean page of the editor and scroll to the WebSphere Extensions section.
  4. Click Start EJB at Application Start:. This option applies to all types of Enterprise Java Beans. This ensures that your EJB is loaded when the application starts.
  5. Click Disable synchronization before finder invocation: The EJB 2.0 specification level introduced the behavior that the EJB containers must persist any changes made to the EJB beans in the current transaction, before running any finder methods. If you are familiar with the API extensions of WebSphere Application Server, this option performs the same functions as the DisableFlushBeforeFind interface. When enabling this option, it provides a performance optimization by disabling the default specification behavior.
    Remember: Enabling this option results in a behavior which is no longer compliant to the EJB specification.
    This option applies to Container Managed Persistence 1.1 Enterprise Java Beans in a 2.x module, to Container Managed Persistence 2.x Enterprise Java Beans in a 2.x module, and to Bean Managed Persistence Enterprise Java Beans in a 2.x module. In other words, this option is valid for BMP, CMP2.x and CMP1.1 in a 2.x module (but is not valid for a BMP or CMP (1.1) Enterprise Java Beans in a 1.1 module).
  6. Click Use Lightweight Local Mode:. This option applies to Container Managed Persistence 2.x Enterprise Java Beans in a 2.x module and to Bean-Managed Persistence Enterprise Java Beans in a 2.x module. In other words, this option is valid for BMP and CMP 2.x in a 2.x module (but is not valid for a CMP 1.1 in a 2.0 module, or BMP or CMP in a 1.1 module).

    To select Use Lightweight Local Mode, the EJB must also contain a local interface (it can also have a remote interface).

  7. Click Disable Enterprise Java Beanstore invocation if EJB is unmodified:. This option applies to Container Managed Persistence 2.x Enterprise Java Beans in a 2.x module. In other words, this option is only valid for CMP 2.x Enterprise Java Beans, but not CMP 1.x beans (even if defined in a 2.x module), and not for BMP Enterprise Java Beans.

Feedback