Ejb Module Not Deploying When Not Exploded

(Doc ID 1314867.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle WebLogic Server - Version 10.0 to 10.0
Information in this document applies to any platform.


With WebLogic Server 10.0 and 10.0MP1, when trying to deploy an exploded ear with a jar file (.zip) defined within the application.xml such as:


Note: EJB class(shipped in the .zip file) defined with annotation

The following exception gets thrown:

<8 mars 2011 12 h 07 CET> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Exception preparing module: EJBModule(myejb.jar.zip)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No  EJBs found in the ejb-jar file 'myejb.jar.zip'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93

However if we explode the content myejb.jar.zip to a directory within the exploded ear directory, update the application.xml DD file and redefine module to point to the directory, then deployment of the ear file is successful.

Thus deploying an exploded ear with an exploded jar file defined within the application.xml works but not with a jar component.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms