Application Client validator
|
CHKJ1000 |
Validation failed because the application client file
is not valid. Ensure that the deployment descriptor is valid. |
The application-client.xml file cannot be loaded. The
project metadata cannot be initialized from the application-client.xml file.
- Ensure the following:
- that the META-INF folder exists in the application client project
- that META-INF contains the application-client.xml file
- that META-INF is in the project's classpath.
- Validate the syntax of the application-client.xml file: in the Navigator
view, highlight the application-client.xml file, right-click, and select Validate
XML file.
- If both 1) and 2) are okay, close the project, reopen the project, and
rebuild the project. The project metadata will refresh.
|
EAR validator
|
CHKJ1001 |
The EAR project {0} is invalid. |
The application.xml file cannot be loaded. The project
metadata cannot be initialized from the application.xml file.
- Ensure the following:
- that the META-INF folder exists in the EAR project
- that META-INF contains application.xml
- that META-INF is in the project's classpath.
- Validate the syntax of the application.xml file: in the Navigator view,
highlight the application.xml file, right-click, and select Validate
XML file.
- If both 1) and 2) are okay, close the project, reopen the project, and
rebuild the project. The project metadata will refresh.
|
EJB validator
|
CHKJ2019 |
The {0} key class must be serializable at runtime. |
The EJB is compliant with the EJB specification. This
message is a warning that problems may occur. The warning appears when a type
needs to be serializable at runtime and when serializability cannot be verified
at compile-time. A type is serializable if, at runtime, it is a primitive
type, a primitive array, a remote object, or if it implements java.io.Serializable.
This message flags java.lang.Object and it cannot be disabled. You can either
make the object serializable at compile-time or ignore the warning. |
CHKJ2412 |
The return type must be serializable at runtime. |
CHKJ2413 |
Argument {1} of {0} must be serializable at runtime. |
CHKJ2102 |
Either a finder descriptor, or a matching custom finder method on the
{0} class, must be defined. |
A finder descriptor must exist for every finder method. |
CHKJ2873 |
Migrate this bean's datasource binding to a CMP Connection Factory
binding. |
|
CHKJ2874 |
Migrate this EJB module's default datasource binding to a default CMP
Connection Factory binding. |
|
CHKJ2875E |
<ejb-client-jar> {0} must exist in every EAR file
that contains this EJB module. |
If <ejb-client-jar> is specified
in ejb-jar.xml, a corresponding EJB client project must
contain the home and remote interfaces and any other types that a client will
need. If these types are all contained in a single EJB project, delete the <ejb-client-jar> line
in the deployment descriptor. Otherwise, ensure that the EJB client project
exists, is open, and is a project utility JAR in every EAR that uses this
EJB project as a module. |
CHKJ2905 |
The EJB validator did not run because ejb-jar.xml could not be loaded.
Run the XML validator for more information. |
CHKJ2905 means that the project's metadata could not be initialized
from ejb-jar.xml.
- Ensure the following:
- that the META-INF folder exists in the EJB project
- that META-INF contains ejb-jar.xml
- that META-INF is in the project's classpath.
- Validate the syntax of the ejb-jar.xml file: in the Navigator view, highlight
the ejb-jar.xml file, right-click, and select Validate XML file.
- If both 1) and 2) are okay, close the project, reopen the project, and
rebuild the project. The project metadata will refresh.
|
JSP validator
|
IWAW0482 |
No valid JspTranslator |
There is a path problem with the project; the JSP Validator
needs access to the WAS runtime code. If IWAW0482E appears on all web projects,
check the Variable or JRE path:
- Check the global preferences (Window > Preferences > Java >Installed
JREs) and make sure that the location for the JRE is pointing
to a valid JRE directory.
- Ensure that the classpath variables (Window > Preferences >
Java > Classpath Variables) are set correctly.
|
WAR validator
|
CHKJ3008 |
Missing or invalid WAR file. |
The web.xml file cannot be loaded. The project metadata
cannot be initialized from the web.xml file.
- Ensure the following:
- that the WEB-INF folder exists in the web project
- that WEB-INF contains the web.xml file
- that WEB-INF is in the project's classpath.
- Validate the syntax of the web.xml file: in the Navigator view, highlight
the web.xml file, right-click, and select Validate XML file.
- If both 1) and 2) are okay, close the project, reopen the project, and
rebuild the project. The project metadata will refresh.
|
XML validator
|
|
The content of element type "ejb-jar" is incomplete, it must match
"(description?,display-name?,small-icon?,large-icon?,enterprise-beans,assembly-descriptor?,ejb-client-jar?)". |
The EJB 1.1 and 2.0 specifications mandate that at least one enterprise
bean must exist in an EJB .jar file. This error message is normal during development
of EJB .jar files and can be ignored until you perform a production action,
such as exporting or deploying code. Define at least one enterprise bean in
the project. |