Hot Deployment of EJBs

Many J2EE containers support hot deployment, a feature that enables you to deploy EJBs on a running server. Hot deployment allows you to:

• Deploy newly-developed EJBs to a running production system

• Remove (undeploy) deployed EJBs from a running server

• Modify (redeploy) the behavior of deployed EJBs by updating the bean class definition

When you take advantage of hot deployment, note the following:

• You must deploy all related beans (all beans that share a common OracleAS TopLink project) within the same EJB JAR file. Because OracleAS TopLink views deployment on a project level, deploy all the project beans (rather than just a portion of them) to maintain consistency across the project.

• When you redeploy a bean, you automatically reset its OracleAS TopLink project. This flushes all object caches and rolls back any active object transactions associated with the project.

The client receives deployment exceptions when attempting to access undeployed or redeployed bean instances. The client application must catch and handle the exceptions.

For more information about hot deployment, see the J2EE container documentation.