diff options
Diffstat (limited to 'docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html')
-rw-r--r-- | docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html | 190 |
1 files changed, 0 insertions, 190 deletions
diff --git a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html b/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html deleted file mode 100644 index 54090d30e..000000000 --- a/docs/org.eclipse.jst.j2ee.doc.user/topics/rvalerr.html +++ /dev/null @@ -1,190 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> - -<title>Common validation errors and solutions</title> -</head> -<body id="rvalerr"><a name="rvalerr"><!-- --></a> -<h1 class="topictitle1">Common validation errors and solutions</h1> -<div><p>You may encounter these common error messages when you validate -your projects.</p> - -<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="20.27027027027027%" id="d0e33">Message prefix</th> -<th valign="top" width="24.324324324324326%" id="d0e35">Message</th> -<th valign="top" width="55.4054054054054%" id="d0e37">Explanation</th> -</tr> -</thead> -<tbody><tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">Application Client validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ1000</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Validation failed because the application client file -is not valid. Ensure that the deployment descriptor is valid.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">The application-client.xml file cannot be loaded. The -project metadata cannot be initialized from the application-client.xml file. - <ol><li>Ensure the following: <ul><li>that the META-INF folder exists in the application client project</li> -<li>that META-INF contains the application-client.xml file</li> -<li>that META-INF is in the project's classpath.</li> -</ul> - </li> -<li>Validate the syntax of the application-client.xml file: in the Navigator -view, highlight the application-client.xml file, right-click, and select <span class="uicontrol">Validate -XML file</span>.</li> -<li>If both 1) and 2) are okay, close the project, reopen the project, and -rebuild the project. The project metadata will refresh.</li> -</ol> - </td> -</tr> -<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">EAR validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ1001</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">The EAR project {0} is invalid.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">The application.xml file cannot be loaded. The project -metadata cannot be initialized from the application.xml file. <ol><li>Ensure the following: <ul><li>that the META-INF folder exists in the EAR project</li> -<li>that META-INF contains <samp class="codeph">application.xml</samp></li> -<li>that META-INF is in the project's classpath.</li> -</ul> - </li> -<li>Validate the syntax of the application.xml file: in the Navigator view, -highlight the application.xml file, right-click, and select <span class="uicontrol">Validate -XML file</span>.</li> -<li>If both 1) and 2) are okay, close the project, reopen the project, and -rebuild the project. The project metadata will refresh.</li> -</ol> -</td> -</tr> -<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">EJB validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2019</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">The {0} key class must be serializable at runtime. </td> -<td rowspan="3" valign="top" width="55.4054054054054%" headers="d0e37 ">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. </td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2412</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">The return type must be serializable at runtime. </td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2413</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Argument {1} of {0} must be serializable at runtime.</td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2102</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Either a finder descriptor, or a matching custom finder method on the -{0} class, must be defined.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">A finder descriptor must exist for every finder method. </td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2873</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Migrate this bean's datasource binding to a CMP Connection Factory -binding.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 "> </td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2874</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Migrate this EJB module's default datasource binding to a default CMP -Connection Factory binding.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 "> </td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2875E </td> -<td valign="top" width="24.324324324324326%" headers="d0e35 "><ejb-client-jar> {0} must exist in every EAR file -that contains this EJB module.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">If <samp class="codeph"><ejb-client-jar></samp> is specified -in <span class="filepath">ejb-jar.xml</span>, 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 <samp class="codeph"><ejb-client-jar></samp> 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.</td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ2905</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">The EJB validator did not run because ejb-jar.xml could not be loaded. -Run the XML validator for more information.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">CHKJ2905 means that the project's metadata could not be initialized -from ejb-jar.xml. <ol><li>Ensure the following: <ul><li>that the META-INF folder exists in the EJB project</li> -<li>that META-INF contains ejb-jar.xml</li> -<li>that META-INF is in the project's classpath.</li> -</ul> - </li> -<li>Validate the syntax of the ejb-jar.xml file: in the Navigator view, highlight -the ejb-jar.xml file, right-click, and select <span class="uicontrol">Validate XML file</span>.</li> -<li>If both 1) and 2) are okay, close the project, reopen the project, and -rebuild the project. The project metadata will refresh.</li> -</ol> -</td> -</tr> -<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">JSP validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">IWAW0482</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">No valid JspTranslator</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">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: <ol><li>Check the global preferences (<span class="uicontrol">Window > Preferences > Java >Installed -JREs</span>) and make sure that the location for the JRE is pointing -to a valid JRE directory. </li> -<li>Ensure that the classpath variables (<span class="uicontrol">Window > Preferences > -Java > Classpath Variables</span>) are set correctly.</li> -</ol> - </td> -</tr> -<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">WAR validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 ">CHKJ3008</td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">Missing or invalid WAR file.</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">The web.xml file cannot be loaded. The project metadata -cannot be initialized from the web.xml file. <ol><li>Ensure the following: <ul><li>that the WEB-INF folder exists in the web project</li> -<li>that WEB-INF contains the web.xml file</li> -<li>that WEB-INF is in the project's classpath.</li> -</ul> - </li> -<li>Validate the syntax of the web.xml file: in the Navigator view, highlight -the web.xml file, right-click, and select <span class="uicontrol">Validate XML file</span>.</li> -<li>If both 1) and 2) are okay, close the project, reopen the project, and -rebuild the project. The project metadata will refresh.</li> -</ol> -</td> -</tr> -<tr><td colspan="3" valign="top" headers="d0e33 d0e35 d0e37 "><span class="uicontrol">XML validator</span></td> -</tr> -<tr><td valign="top" width="20.27027027027027%" headers="d0e33 "> </td> -<td valign="top" width="24.324324324324326%" headers="d0e35 ">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?)".</td> -<td valign="top" width="55.4054054054054%" headers="d0e37 ">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.</td> -</tr> -</tbody> -</table> -</div> -</div> -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tjval.html">Validating code in enterprise applications</a></div> -</div> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-ref.html" title="The following reference material on J2EE is available:">Reference</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tjval.html">Validating code in enterprise applications</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rvalidators.html" title="This table lists the validators that are available for the different project types and gives a brief description of each validator.">J2EE Validators</a></div> -</div> -</div></body> -</html>
\ No newline at end of file |