JSPG

JSPG0234E: The JSP container is unable to locate the Java archive (JAR) resource [{0}] to parse tag library descriptors (TLDs).

Explanation

A tag library URI that is defined as a JAR location (web.xml file or page directive) cannot be located.

Action

Verify that the JAR file exists and is accessible to this Web module.

JSPG0235E: The JSP container failed to load the TagExtraInfo class [{0}]

Explanation

The JSP container is unable to load the TagExtraInfo class that is specified in the tag library descriptor (TLD).

Action

Verify that the TagExtraInfo class exists and is accessible to this Web module.

JSPG0236E: The JSP container failed to load the TagLibraryValidator class [{0}]

Explanation

The JSP container is unable to load the TagLibraryValidator class that is specified in the tag library descriptor (TLD).

Action

Verify that the TagLibraryValidator class exists and is accessible to this Web module.

JSPG0237E: Cannot find an attribute directive with a name attribute with a value "{0}", the value of this name-from-attribute attribute.

Explanation

Explanation

Action

User Action

JSPG0238E: The attribute directive (declared in line {0} and whose name attribute is "{1}", the value of this name-from-attribute attribute) must be of type java.lang.String, is "required" and not a "rtexprvalue".

Explanation

Explanation

Action

User Action

JSPG0239E: <jsp:output>: illegal to have multiple occurrences of "{0}" with different values (old: {1}, new: {2})

Explanation

<jsp:output> contains multiple occurrences of the attribute and they have different values.

Action

Be sure multiple occurrences of the attribute have the same value.

JSPG0240E: Attempt to redefine the prefix "{0}" to "{1}", when it was already defined as "{2}" in the current scope.

Explanation

The taglibrary prefix was already defined with a different URI.

Action

Make sure the prefix is defined with only one URI.

JSPG0241E: The prefix "{0}" specified in this tag directive has been previously used by an action in file {1}.

Explanation

The taglibrary prefix was used before the tag directive that defines the prefix.

Action

Move the tag directive above all actions that use the prefix.

JSPG0298E: The PageContext has already been initialized or released.

Explanation

The JSP container handles the initializing and releasing of PageContext objects.

Action

According to the specification, verify that there are no applications using JspFactory objects.

JSPG0299E: The dynamic attribute {0} has a prefix that does not map to a namespace.

Explanation

The dynamic attribute prefix does not map to a namespace.

Action

Make sure the prefix maps to an existing namespace.

JSPG0300E: Unable to get a RequestDispatcher for context: {0}

Explanation

Unable to get a RequestDispatcher for the requested context.

Action

Verify tag values are correct and verify that the requested context exists.

JSPG0301E: Invalid attribute, {0}, for deferred method returning void.

Explanation

The attribute passed to a deferred method returning void can not be a string literal.

Action

Modify the value passed in for the attribute.

JSPG0302W: Failed to load the following JSP class: {0}, the exception is: {1}

Explanation

There was a problem loading the JSP class. The JSP Container will attempt to load the class file with the org.apache.jsp package name instead.

Action

If the problem persists, restart the application.

JSPG0303W: The system was not able to parse the following JSP Tag Library Descriptor: {0}. The exception for the parsing error is: {1}

Explanation

A problem occurred when parsing the JSP Tag Library Descriptor file. This error can be caused by a malformed XML file.

Action

Check the JSP Tag Library Descriptor file for malformed XML. If the problem persists after correcting the malformed XML file, restart the application.

JSPG0304W: The JSP attribute, useJDKCompiler, is set to true, but the Java SDK compiler was not found. The JSP container uses the compiler that is embedded in the product to compile the JSP files in web module: {0}.

Explanation

The JSP container was unable to find the system compiler, which usually indicates that the Java SDK jar file, tools.jar, was not found in the class path.

Action

Ensure that the Java SDK jar file, tools.jar, is in the class path and verify that the Java SDK supports the Java Compiler API. See Java Specification Request 199 for more information.

JSPG8500W: JDK 7 is not in use even though jdkSourceLevel was specified to be 17.

Explanation

A request was made to compile jsps at a level not supported.

Action

Either install JDK 7 or change the jdkSourceLevel to 16.

JSPG8501W: Exception thrown checking the java.version property

Explanation

There was a problem parsing the java.version property.

Action

Verify the java version is valid.