JSPG

JSPG0001E: jsp:params has invalid parent tag
Explanation
Action
JSPG0002E: jsp:fallback has invalid parent tag
Explanation
Action
JSPG0003E: jsp:param has invalid parent tag
Explanation
Action
JSPG0004E: jsp:param name attribute cannot be empty
Explanation
Action
JSPG0005E: tld file could not be found for uri[{0}] prefix [{1}]
Explanation
Action
JSPG0006E: Custom Tag is missing required attribute {0}
Explanation
Action
JSPG0007E: Custom Tag has missing attribute {0}
Explanation
Action
JSPG0008E: Custom Tag has invalid attributes
Explanation
Action
JSPG0009E: Unable to load tag handler class {0}
Explanation
Action
JSPG0010E: jsp:root element has no attributes
Explanation
Action
JSPG0011E: jsp:useBean is missing an id attribute
Explanation
Action
JSPG0012E: jsp:useBean is missing a type attribute or class attribute
Explanation
Action
JSPG0013E: A bean with id {0} has already been defined
Explanation
Action
JSPG0014E: scope attribute cannot be "session" if session page directive is false
Explanation
Action
JSPG0015E: jsp:useBean cannot have both a class and a beanName attribute (class = [{0}] beanName =[{1}]).
Explanation
Action
JSPG0016E: invalid scope attribute value. Must page, request, session or application. Scope specified {0}.
Explanation
Action
JSPG0017E: jsp:useBean contains no attributes
Explanation
Action
JSPG0018E: Expression contains no text
Explanation
Action
JSPG0019E: Invalid value for session directive
Explanation
Action
JSPG0020E: Invalid value for buffer directive
Explanation
Action
JSPG0021E: Invalid value for autoflush directive
Explanation
Action
JSPG0022E: Invalid value for threadsafe directive
Explanation
Action
JSPG0023E: Invalid value for iserrorpage attribute
Explanation
Action
JSPG0024E: Unknown directive {0}
Explanation
Action
JSPG0025E: Page directive contains no attributes
Explanation
Action
JSPG0026E: Scriptlet contains no text
Explanation
Action
JSPG0027E: Declaration contains no text
Explanation
Action
JSPG0028E: jsp:text contains no text
Explanation
Action
JSPG0029E: invoke action can only be used in tag files
Explanation
Action
JSPG0030E: doBody action can only be used in tag files
Explanation
Action
JSPG0031E: tag directive can only be used in tag files
Explanation
Action
JSPG0032E: attribute directive can only be used in tag files
Explanation
Action
JSPG0033E: variable directive can only be used in tag files
Explanation
Action
JSPG0034E: xml dtd or schema not found
Explanation
Action
JSPG0035E: page encoding in jsp configuration does not match one in jsp
Explanation
Action
JSPG0036E: Failed to find resource {0}
Explanation
Action
JSPG0037E: Invalid value for isELIgnored attribute
Explanation
Action
JSPG0038E: Invalid value for dynamicAttributes directive
Explanation
Action
JSPG0039E: page directive can only be used in page files
Explanation
Action
JSPG0040E: {0} has already been statically included
Explanation
Action
JSPG0041E: Expression language function class not found. {0} {1} {2}
Explanation
Action
JSPG0042E: Parenthesis expected for expression language function {0} {1}
Explanation
Action
JSPG0043E: Invalid signature for expression language function {0} {1}
Explanation
Action
JSPG0044E: Comma expected for expression language function {0} {1}
Explanation
Action
JSPG0045E: Error while retrieving bean information for {0}
Explanation
Action
JSPG0046E: Unable to locate tagfile for tag {0}
Explanation
Action
JSPG0047E: Unable to locate tag library for uri {0}
Explanation
Action
JSPG0048E: Page failed to validate using taglib validator for {0} : {1}
Explanation
Action
JSPG0049E: {0} failed to compile : {1}
Explanation
Action
JSPG0050E: tld file could not be found at location {0}
Explanation
Action
JSPG0051E: Duplicate Page Directive value : {0}
Explanation
Action
JSPG0052E: Duplicate Tag Directive value : {0}
Explanation
Action
JSPG0053E: Include preludes are not allowed in Jsp Documents
Explanation
Action
JSPG0054E: Include codas are not allowed in Jsp Documents
Explanation
Action
JSPG0055E: Unable to create an xml attribute from name [{0}] value [{1}]
Explanation
Action
JSPG0056E: Unable to create an xml element from namespace [{0}] name [{1}]
Explanation
Action
JSPG0057I: JspModC -appDir <path> -tmpDir <path> -forceTranslation <true/false> -additionalClasspath <classpath> -jspFile <jspFile>
Explanation
Action
JSPG0058I: IBM JSP 2.1 Engine
Explanation
Action
JSPG0060E: Invalid jsp syntax [{0}]
Explanation
Action
JSPG0061E: Attribute {0} is unrecognised for jsp element {1}
Explanation
Action
JSPG0062E: Request-time Attribute {0} is unrecognised for jsp element {1}
Explanation
Action
JSPG0063E: Invalid value for language directive {0}
Explanation
Action
JSPG0064E: Invalid value for buffer directive valid values. If value other than none, suffix kb is required
Explanation
Action
JSPG0065E: Illegal use of EL tag. Nesting of EL tags are not permitted
Explanation
Action
JSPG0066E: Failed to parse Expression Language tag {0}
Explanation
Action
JSPG0067E: Illegal use of EL Tag. Value "{2}" is not permitted for attribute "{1}" for jsp element {0}
Explanation
Action
JSPG0068E: Unmatched tag found while parsing jsp [{0}]
Explanation
Action
JSPG0069E: Unmatched end tag found while parsing jsp. Expecting {0} found {1} at {2}
Explanation
Action
JSPG0070E: Duplicate url pattern [{0}] found in the Web Applications Jsp Configuration
Explanation
Action
JSPG0071E: Failed to load tld from webinf resource {0} msg: {1}
Explanation
Action
JSPG0072E: Failed to load tld from jar {0} resource {1} msg: {2}
Explanation
Action
JSPG0073E: useBean class "{0}" must be assignable to type "{1}" for jsp element {2}
Explanation
Action
JSPG0074E: Cannot locate class to determine if useBean class "{0}" is assignable to type "{1}" for jsp element {2}
Explanation
Action
JSPG0075E: Multiple occurences of attribute {0} not permitted for jsp element {1}
Explanation
Action
JSPG0076E: Missing required attribute {0} for jsp element {1}
Explanation
Action
JSPG0077E: End of file reached while processing {0} at {1}
Explanation
Action
JSPG0078E: Invalid value for tag directive attribute body-content. value {0}
Explanation
Action
JSPG0079E: Multiple occurrences of attribute name or alias or name-given "{2}" not permitted. "{2}" specified in jsp elements "{0}" and "{1}"
Explanation
Action
JSPG0080E: Tag file variable directive cannot have both a name-given and name-from-attribute attribute (name-given=[{1}] name-from-attribute=[{2}]) jsp element {0}.
Explanation
Action
JSPG0081E: Tag file variable directive requires either a name-given or name-from-attribute attribute for jsp element {0}.
Explanation
Action
JSPG0082E: Invalid value for variable directive attribute scope "{1}" jsp element {0}.
Explanation
Action
JSPG0083E: Missing required atribute alias when name-from-attribute "{1}" specified jsp element {0}
Explanation
Action
JSPG0084E: Attribute alias "{2}" not permitted if name-given "{1}" specified. jsp element {0}
Explanation
Action
JSPG0085E: Error while load class specified for tag attibute for {0}
Explanation
Action
JSPG0086E: Static Include {0} must be of the same type as the including jsp.
Explanation
Action
JSPG0087E: Mismatch found between jsp config encoding {0} and xml prolog encoding {1}
Explanation
Action
JSPG0088E: Mismatch found between jsp config encoding {0} and page directive encoding {1}
Explanation
Action
JSPG0089E: Mismatch found between page directive encoding {0} and xml prolog encoding {1}
Explanation
Action
JSPG0090E: Error pageEncoding has already been supplied for this jsp
Explanation
Action
JSPG0091E: An error occurred at line: {0} in the file: {1}
Explanation
Action
JSPG0092E: An error occurred between lines: {0} and {1} in the file: {2}
Explanation
Action
JSPG0093E: Generated servlet error from file: {0}
Explanation
Action
JSPG0094E: Unable to locate the prefix for el function {0}
Explanation
Action
JSPG0095E: Unable to locate the el function {0} in the tld with uri {1}
Explanation
Action
JSPG0096E: Failed to load {0}
Explanation
Action
JSPG0097E: Failed to load el function method {0}
Explanation
Action
JSPG0098E: jsp:output tag cannot have a body
Explanation
Action
JSPG0099E: jsp:root version attribute is invalid : {0}
Explanation
Action
JSPG0100E: Name of Dynamic Attributes Map is the same as the tag attribute directive name attribute
Explanation
Action
JSPG0101E: Name of Dynamic Attributes Map is the same as the tag varibke directive name-given attribute
Explanation
Action
JSPG0102E: jsp:text cannot have child elements
Explanation
Action
JSPG0105E: The {0} tag can only have jsp:attribute in its body. Found: {1}
Explanation
Action
JSPG0106E: The jsp:output element can only be used in JSP documents and in tag files in XML syntax.
Explanation
Action
JSPG0107E: The jsp:attribute element with value of type JspFragment cannot contain scriptlets {0}.
Explanation
Action
JSPG0108E: Illegal to specify rtexprvalue for attribute of type fragment. rtexprvalue: {0}
Explanation
Action
JSPG0109E: Illegal to specify type for attribute of type fragment. type: {0}
Explanation
Action
JSPG0110E: Illegal to specify type as primitive Class for tag file attribute. primitive {0}
Explanation
Action
JSPG0111E: Unable to verify tag file attribute type {0} is not a primitive Class.
Explanation
Action
JSPG0112E: Scripting in runtime expressions disabled for this translation unit.
Explanation
Action
JSPG0113E: Scriptlets disabled for this translation unit.
Explanation
Action
JSPG0114E: Declarations disabled for this translation unit.
Explanation
Action
JSPG0115E: Expressions disabled for this translation unit.
Explanation
Action
JSPG0116E: Illegal to specify page directive {0} more than once if they have different values. first: {1} second: {2}
Explanation
Action
JSPG0117E: Illegal to specify uri in conjunction with tagdir in taglib directive. uri: "[{0}]" tagdir: "[{1}]"
Explanation
Action
JSPG0118E: Illegal to specify multiple occurrences of uri in taglib directive. uri: "[{0}]" uri: "[{1}]"
Explanation
Action
JSPG0119E: Illegal to specify multiple occurrences of tagdir in taglib directive. tagdir: "[{0}]" tagdir: "[{1}]"
Explanation
Action
JSPG0120E: Illegal to specify different values for pageEncoding attribute and configuration element for matching URI pattern. directive: "[{0}]" configuration: "[{1}]"
Explanation
Action
JSPG0121E: Illegal to use <jsp:attribute> to define the value of an attribute of <jsp:attribute>
Explanation
Action
JSPG0122E: Unable to parse EL function {0}.
Explanation
Action
JSPG0123E: Unable to locate tag attribute info for tag attribute {0}.
Explanation
Action
JSPG0124E: According to TLD or attribute directive in tag file, attribute "[{0}]" does not accept any expressions. Value of expression is: "[{1}]".
Explanation
Action
JSPG0125E: Custom tag attribute {0} cannot be runtime fragment.
Explanation
Action
JSPG0126E: jsp {0} cannot contain more than one pageEncoding directive
Explanation
Action
JSPG0127E: Illegal to specify tag directive {0} more than once. first: {1} second: {2}
Explanation
Action
JSPG0128E: Unable to translate JSP {0}.
Explanation
Action
JSPG0129E: JspServlet failed to initialize
Explanation
Action
JSPG0130E: Invalid value for the flush attribute: {0}
Explanation
Action
JSPG0131E: Error non-null tei and variable subelements found
Explanation
Action
JSPG0132E: Invalid Attributes found for {0} {1}. Error is {2}
Explanation
Action
JSPG0133E: Parent of jsp:attribute must be either a standard or custom action
Explanation
Action
JSPG0134E: Parent of jsp:body is invalid
Explanation
Action
JSPG0135E: Parent of jsp:body is is a custom tag that has specified it has no body in its tld
Explanation
Action
JSPG0136E: jsp:invoke cannot have both var and varReader set
Explanation
Action
JSPG0137E: jsp:doBody cannot have both var and varReader set
Explanation
Action
JSPG0138E: jsp:invoke must have either var and varReader set when scope is set
Explanation
Action
JSPG0139E: jsp:doBody must have either var and varReader set when scope is set
Explanation
Action
JSPG0140E: jsp:invoke scope value is invalid
Explanation
Action
JSPG0141E: jsp:doBody scope value is invalid
Explanation
Action
JSPG0142E: Runtime Expr Value "{2}" is not permitted for attribute "{1}" for jsp element {0}
Explanation
Action
JSPG0143E: name attribute of jsp:attribute has different prefix to parent : {0} not equal {1}
Explanation
Action
JSPG0144E: Invalid value for plugin "type" attribute : {0}
Explanation
Action
JSPG0145E: Unknown JSP element : {0}
Explanation
Action
JSPG0146E: Invalid attribute for include directive : {0}
Explanation
Action
JSPG0147E: Missing required attribute "file" for include directive.
Explanation
Action
JSPG0148E: JSP file does not exist: {0}
Explanation
Action
JSPG0149E: Target directory does not exist: {0}
Explanation
Action
JSPG0150E: Target directory name is not a directory: {0}
Explanation
Action
JSPG0151I: Return code: {0}
Explanation
Action
JSPG0152E: Unable to create classloader.
Explanation
Action
JSPG0153I: Initializing server...
Explanation
Action
JSPG0154E: Exception caught while processing command-line arguments.
Explanation
Action
JSPG0155E: Unknown command-line argument: {0}
Explanation
Action
JSPG0156W: Unknown log level {0}, using default {1}
Explanation
Action
JSPG0157I: Cell name not supplied; using default: {0}
Explanation
Action
JSPG0158I: Node name not supplied; using default: {0}
Explanation
Action
JSPG0159I: Server name not supplied; using default: {0}
Explanation
Action
JSPG0160I: Compiling all webmodules
Explanation
Action
JSPG0161E: Unable to initialize server.
Explanation
Action
JSPG0162E: Exception caught while adding ComponentManager service.
Explanation
Action
JSPG0163E: Exception caught while initializing batch compiler service.
Explanation
Action
JSPG0164E: Repository service not available.
Explanation
Action
JSPG0165I: Reading config file...

Explanation
Action
JSPG0166E: Enterprise Application not found: {0}
Explanation
Action
JSPG0167I: Finished reading config file.
Explanation
Action
JSPG0168I: The Batch Compiler exited successfully without errors.
Explanation
Action
JSPG0169I: The Batch Compiler exited with errors.
Explanation
Action
JSPG0170E: Error reading configuration: {0} {1}
Explanation
Action
JSPG0171E: Error while finding Server.
Explanation
Action
JSPG0172E: Error while finding enterprise app.
Explanation
Action
JSPG0173E: extractToDir directory is not writable: {0}
Explanation
Action
JSPG0174E: extractToDir directory is not a directory: {0}
Explanation
Action
JSPG0175E: Exception caught while extracting earfile {0}.
Explanation
Action
JSPG0176E: WAR path does not exist: {0}
Explanation
Action
JSPG0177E: WAR path is not a file: {0}
Explanation
Action
JSPG0178E: EAR path does not exist: {0}
Explanation
Action
JSPG0179E: EAR path is not a file: {0}
Explanation
Action
JSPG0180E: Webmodule not found: {0}
Explanation
Action
JSPG0183I: Removing {0}
Explanation
Action
JSPG0184I: Extracting {0} to {1}
Explanation
Action
JSPG0185I: Done extracting.
Explanation
Action
JSPG0186I: Saving {0}
Explanation
Action
JSPG0187I: Done saving.
Explanation
Action
JSPG0188E: Exception encountered during save operation.
Explanation
Action
JSPG0192E: No EAR path or WAR path or Enterpise App name was given. Must supply one of these.
Explanation
Action
JSPG0193E: Must supply only one of EAR path or WAR path or Enterprise App.
Explanation
Action
JSPG0194W: Webmodule name {0} being ignored because WAR path was given.
Explanation
Action
JSPG0195E: Exception caught while extracting warfile: {0}.
Explanation
Action
JSPG0196E: JSP Batch Compiler extractToDir must not overlap with ear path.
Explanation
Action
JSPG0197E: JSP Batch Compiler extractToDir must not overlap with war path.
Explanation
Action
JSPG0198E: extractToDir does not exist: {0}
Explanation
Action
JSPG0199E: Exception caught getting warfile list
Explanation
Action
JSPG0200E: Exception caught opening earfile
Explanation
Action
JSPG0202E: Exception caught opening warfile
Explanation
Action
JSPG0203W: ExtractToDir {0} being ignored because enterpriseapp.name was given.
Explanation
Action
JSPG0204W: Exception caught when adding variable map. {0}
Explanation
Action
JSPG0205W: Error creating order of JSP visitors. {0}
Explanation
Action
JSPG0206E: Error loading jsp-visitor-definition
Explanation
Action
JSPG0207E: Exception caught while processing command-line arguments: File: {0} Message: {1}
Explanation
Action
JSPG0208W: compileToWebInf being ignored because compileToDir {0} was given.
Explanation
Action
JSPG0209E: {0}(0,0) failed to read JSP: {1}
Explanation
Action
JSPG0210E: autoFlush cannot be set to false when buffer is set to none
Explanation
Action
JSPG0211E: jsp:root must be top element in document
Explanation
Action
JSPG0212E: jsp:root can only be used in JSP Documents
Explanation
Action
JSPG0213E: Error must provide a doctype-root-element when using doctype-system attribute
Explanation
Action
JSPG0214E: Error doctype-system is not provided.
Explanation
Action
JSPG0215E: Error failed to create configured translation context from {0}. Exception : {2}
Explanation
Action
JSPG0216E: Error failed to load configured context class {0}
Explanation
Action
JSPG0217E: Error failed to load configured extension processor class {0}
Explanation
Action
JSPG0218E: Error failed to locate setter method for attribute {1} in tag class {0}
Explanation
Action
JSPG0219E: Error taglib directive attribute {0} with value {1} is unknown.
Explanation
Action
JSPG0220E: Error taglib directive missing required attribute prefix.
Explanation
Action
JSPG0221E: Compiling a JSP in META-INF not allowed. File: {0}
Explanation
Action
JSPG0222E: If removeTempDir is true, enterpriseApp.name must be given.
Explanation
Action
JSPG0223E: If translate is false, removeTempDir must be true.
Explanation
Action
JSPG0224W: JSP Engine parameter scratchdir [{0}] is being ignored because ear.path or war.path was given.
Explanation
Action
JSPG0225E: An error occurred at line: {0} in the statically included file: {1}
Explanation
Action
JSPG0226E: An error occurred between lines: {0} and {1} in the statically included file: {2}
Explanation
Action
JSPG0227E: Exception caught while translating {0}
Explanation
Action
JSPG0228E: Exception caught while translating {0}: error in statically included file {1}
Explanation
Action
JSPG0233E: Exception caught while getting configuration options.
Explanation
Action
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.
JSPG0242E: Invalid value for trimDirectiveWhitespaces attribute
Explanation
Action
JSPG0243E: Invalid value for deferredSyntaxAllowedAsLiteral attribute
Explanation
Action
JSPG0244E: "{0}" is not allowed in template text.
Explanation
Action
JSPG0245E: Page directive: illegal to have multiple occurrences of ''deferredSyntaxAllowedAsLiteral'' with different values (old: {0}, new: {1})
Explanation
Action
JSPG0246E: Tag directive: illegal to have multiple occurrences of ''deferredSyntaxAllowedAsLiteral'' with different values (old: {0}, new: {1})
Explanation
Action
JSPG0247E: Page directive: illegal to have multiple occurrences of ''trimDirectiveWhitespaces'' with different values (old: {0}, new: {1})
Explanation
Action
JSPG0248E: Tag directive: illegal to have multiple occurrences of ''trimDirectiveWhitespaces'' with different values (old: {0}, new: {1})
Explanation
Action
JSPG0249E: Tag directive: illegal to have multiple occurrences of the attribute "{0}" with different values (old: {1}, new: {2})
Explanation
Action
JSPG0250E: Invalid body-content ({0}) in tag directive.
Explanation
Action
JSPG0251E: Cannot specify a value type if 'deferredValue' is not 'true'
Explanation
Action
JSPG0252E: Cannot specify a method signature if 'deferredMethod' is not 'true'
Explanation
Action
JSPG0253E: 'deferredValue' and 'deferredMethod' cannot be both 'true'
Explanation
Action
JSPG0254E: Invalid JSP version defined for tag file at {0}
Explanation
Action
JSPG0255E: Unknown attribute type ({1}) for attribute {0}.
Explanation
Action
JSPG0256E: Cannot coerce value ({2}) to type ({1}) for attribute {0}.
Explanation
Action
JSPG0257E: White space is required before the version pseudo attribute in the text declaration.
Explanation
Action
JSPG0258E: White space is required before the version pseudo attribute in the XML declaration.
Explanation
Action
JSPG0259E: XML version "{0}" is not supported, only XML 1.0 is supported.
Explanation
Action
JSPG0260E: The encoding declaration is required in the text declaration.
Explanation
Action
JSPG0261E: The version is required in the XML declaration.
Explanation
Action
JSPG0262E: White space is required before the encoding pseudo attribute in the text declaration.
Explanation
Action
JSPG0263E: White space is required before the encoding pseudo attribute in the XML declaration.
Explanation
Action
JSPG0264E: The '' = '' character must follow "{0}" in the text declaration.
Explanation
Action
JSPG0265E: The '' = '' character must follow "{0}" in the XML declaration.
Explanation
Action
JSPG0266E: The value following "{0}" in the text declaration must be a quoted string.
Explanation
Action
JSPG0267E: The value following "{0}" in the XML declaration must be a quoted string.
Explanation
Action
JSPG0268E: An invalid XML character (Unicode: 0x{0}) was found in the text declaration.
Explanation
Action
JSPG0269E: An invalid XML character (Unicode: 0x{0}) was found in the XML declaration.
Explanation
Action
JSPG0270E: closing quote in the value following "{0}" in the text declaration is missing.
Explanation
Action
JSPG0271E: closing quote in the value following "{0}" in the XML declaration is missing.
Explanation
Action
JSPG0272E: Given byte order for encoding "{0}" is not supported.
Explanation
Action
JSPG0273E: Invalid encoding name "{0}".
Explanation
Action
JSPG0274E: White space is required before the encoding pseudo attribute in the XML declaration.
Explanation
Action
JSPG0275E: The standalone document declaration value must be "yes" or "no", not "{0}".
Explanation
Action
JSPG0276E: no more pseudo attributes is allowed.
Explanation
Action
JSPG0277E: more pseudo attributes is expected.
Explanation
Action
JSPG0278E: The XML declaration must end with "?>".
Explanation
Action
JSPG0279E: a pseudo attribute name is expected.
Explanation
Action
JSPG0280E: The processing instruction target matching "[xX][mM][lL]" is not allowed.
Explanation
Action
JSPG0281E: White space is required between the processing instruction target and data.
Explanation
Action
JSPG0282E: An invalid XML character (Unicode: 0x{0}) was found in the processing instruction.
Explanation
Action
JSPG0283E: An invalid XML character (Unicode: 0x{0}) was found in the element content of the document.
Explanation
Action
JSPG0284E: Operation "{0}" not supported by {1} reader.
Explanation
Action
JSPG0285E: Byte "{0}" not 7-bit ASCII.
Explanation
Action
JSPG0286E: Expected byte {0} of {1}-byte UTF-8 sequence.
Explanation
Action
JSPG0287E: Invalid byte {0} of {1}-byte UTF-8 sequence.
Explanation
Action
JSPG0288E: High surrogate bits in UTF-8 sequence must not exceed 0x10 but found 0x{0}.
Explanation
Action
JSPG0289E: Page-encoding specified in XML prolog ({0}) is different from that specified in jsp-property-group ({1})
Explanation
Action
JSPG0290E: Tag file directory {0} does not start with "/WEB-INF/tags"
Explanation
Action
JSPG0291E: Invalid implicit TLD for tag file at {0}; invalid element= [{1}].
Explanation
Action
JSPG0292E: Invalid JSP version defined in implicit TLD for tag file at {0}; version=[{1}].
Explanation
Action
JSPG0293E: ARDRequestDispatcher is null.
Explanation
Action
JSPG0294E: ARD Fragment is null.
Explanation
Action
JSPG0295E: Object is not a FragmentResponse.
Explanation
Action
JSPG0296E: ARD Fragment doesn't exist in the specified scope.
Explanation
Action
JSPG0297E: There is a problem with the import tag. The url attribute and/or the var attribute need(s) to be set.
Explanation
Action
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 doesnÆt 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.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Sep 20, 2012 7:41:11 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.jsp.resources.messages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)