Express (Distributed operating systems), v8.0 > Reference > Messages
CWMDF
CWMDF0001E: Component {0} already exists.
Explanation Component names must be unique. Action This error indicates a severe error condition internal to WebSphere. Report this problem to WebSphere Support.
CWMDF0002E: Annotation processing failed with the following error: {0}
Explanation Processing of annotations failed. Possibly the ear, jar, or war was not packaged properly. Action See exception or error message for possible action.
CWMDF0003E: The {0} business interface class cannot be both remote and local.
Explanation A business interfaces cannot be defined within XML or annotations as both remote and local. Action Determine if business interface should be remote or local and fix the annotations or XML.
CWMDF0004E: Bean class {0} must not contain both @Local and @Remote annotations, each with no parameters
Explanation If both @Remote and @Local annotations are put on a bean class, one or the other must specify the business interface as a parameter. Action Add the name of the business interface to eithe the @Remote or @Local annotations.
CWMDF0005E: The implements clause on Bean class {0} contains multiple interfaces and the bean class has a @Remote or @Local annotation contains no parameters.
Explanation We can only define one business interface on the implements clause of a bean class if the @Remote or @Local annotation has no parameters. Action Ensure the implements clause of the bean class contains only one business interface or change the @Remote or @Local annotation to list the business interfaces as parameters.
CWMDF0006E: Session bean "{0}" has been defined as "{1}" in XML and "{2}" in annotations.
Explanation A session bean must not be defined to be both stateful and stateless. For example: a session bean cannot contain a @Stateless annotation and be defined with a Session type of stateful in XML. Action Check the source code annotation and ejb-jar.xml configuration settings for this bean. Ensure that the session type defined in XML matches the type defined in annotations or remove the @Stateful or @Stateless annotation.
CWMDF0007E: Ear {0} failed to open with the following exception: {1}.
Explanation Ear file failed to open. Possibly the ear file was not packaged properly. Action See exception or error message and fix ear file.
CWMDF0008W: Class {0} failed to load with the following exception: {1}.
Explanation Class failed to load. Possibly the class depends on a class that is not within the scope of the ArchiveClassLoader. Action See exception or error message. Possibly add missing jar file to the Class-Path within the Manifest.mf file.
CWMDF0009W: Methods of class {0} failed to load with the following exception: {1}.
Explanation Methods failed to load for the specified class. Possibly the class contains a method whose signature or parameters are not within the scope of the ArchiveClassloader. Action See exception or error message. Possibly add missing jar file to the Class-Path within the Manifest.mf file.
CWMDF0011E: @MessageDrivenAnnotation has an @AnnotationConfigProperty sub-annotation with a duplicate property: {0}.
Explanation All properties on the @ActivationConfigProperty annotations must be unique. Action Check the @MessageDrivenAnnotation and remove or change duplicate property name on @ActivationConfigProperty sub-annotation.
CWMDF0012E: The bean class {0} for EJB {1} is not found.
Explanation A bean class that has been defined in XML for an EJB cannot be found in the ear. Action Check the XML for the EJB and ensure that the ejb class exists within the ear.
CWMDF0013E: The {0} Enterprise JavaBean (EJB) in the {1} module is defined by the {2} class and the {3} class.
Explanation The same EJB is defined using an annotation on two separate classes. Action Remove the annotation from one of the classes, change the beanName for the annotation on one of the classes, or specify an ejb-class for the bean in the deployment descriptor.
CWMDF0014E: The {0} bean has been defined as the {1} transaction management type in XML and the {2} transaction management type in annotations.
Explanation Do not define an EJB to use both CONTAINER and BEAN-managed transactions. Action Check the @TransactionManagement annotation and ejb-jar.xml configuration settings for this bean. Ensure that the transaction management type that is defined in XML matches the type that is defined in the annotation or remove one of the two settings.
CWMDF0015E: The class loader cannot load the {0} interface on the {1} EJB file.
Explanation All interface classes must be in the same JAR file as the EJB file; inside a defined library directory; or in a JAR file specified in the manifest class path of the EJB jar file. Action Ensure that the jar file containing the interface is either contained in a defined library directory for this EJB or specified in the Class-Path within the Manifest.mf file for this EJB jar file.
CWMDF0016I: This message is an English-only Informational message: {0}.
Explanation This informational message is not translated. Action See message for details.
CWMDF0017W: This message is an English-only Warning message: {0}.
Explanation This warning message is not translated. Action See message for details.
CWMDF0018E: This message is an English-only Error message: {0}.
Explanation This error message is not translated. Action See message for details.
CWMDF0019E: The product does not support container-managed persistence (CMP) Entity beans in EJB 3.0-level modules. The {0} bean in the {1} module must be moved to an EJB 2.1 or earlier-level module.
Explanation CMP Entity beans are supported by the product in EJB 2.1 or earlier-level modules only. Action Package all CMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application.
CWMDF0020E: Bean "{0}" has been annotated with "{1}" and "{2}" annotations.
Explanation An EJB must not be annotated with multiple ejb type annotations. For example: a session bean cannot contain a @Stateless annotation and @MessageDriven annotation. Action Check the source code annotations for this bean. Remove any multiple ejb type annotations.
CWMDF0021E: The product does not support bean-managed persistence (BMP) Entity beans in EJB 3.0-level modules. The {0} bean in the {1} module must be moved to an EJB 2.1 or earlier-level module.
Explanation BMP Entity beans are supported by the product in EJB 2.1 or earlier-level modules only. Action Package all BMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application.
CWMDF0022W: An attempt to scan class file "{0}" in JAR file "{1}" failed with exception: "{2}".
Explanation An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted. Action Ensure that the class file is not corrupted.
CWMDF0023W: An attempt to scan a class file in the directory "{0}" failed with exception: "{1}".
Explanation An attempt to byte-code scan a class file for Java annotations has failed. It is likely that a class file is corrupted. Action Ensure that the class files in the specified directory are not corrupted.
CWMDF0024W: An attempt to scan class file "{0}" in module "{1}" failed with exception: "{2}".
Explanation An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted. Action Ensure that the class file is not corrupted.
CWMDF0025E: Entity beans in EJB Web archive (WAR) modules are not allowed, per the EJB 3.1 specification.
Explanation Entity beans are supported by the EJB 3.1 specification in stand-alone modules only. Action Package all entity beans in stand-alone modules, and reinstall the application.
CWMDF9000E: Error: Unexpected exception "{0}" occurred.
Explanation An unexpected exception occured during command processing. Action Add the -verbose option to see more information.