Limitations of EJB deployment

This topic outlines current, known limitations and restrictions for EJB deployment.

Running older versions of code generation tools

This limitation is applicable to applications that makes use of WebSphere® extensions and bindings. However, if your application does not make use of any of the WebSphere extensions and bindings; and only implements code from the J2EE specifications, than this limitation is not applicable. Hereafter in this limitation, the term "application" defines an enterprise application that makes use of WebSphere extensions and bindings.

When an application is coming from a newer version of the product, you cannot run code generation tools from an older version of the application server. For example, if a EJB application that makes use of WebSphere extensions or bindings is developed in version 6.x of this product, you cannot run ejbDeploy command from WebSphere Application Server v5.x.

The application developed in the newer version of the product may include additional functions or fixes that are not recognized in older code generation tools.

Instead, use the code generation tools from the newer version of the product to package the application as a deployable enterprise artifact (EAR) file. The newer version of the development products provide binary compatibility support to older runtime servers as long as the server supports the J2EE specification level and technology used in the application.

EJB mapping limitations and restrictions

Arabic characters not supported for Java files and enterprise beans

Do not use Arabic characters in names for Java™ files, enterprise beans, or access beans.

Feedback