jsp messages

JSPG0001E: jsp:params has invalid parent tag
Explanation:
User Response:

JSPG0002E: jsp:fallback has invalid parent tag
Explanation:
User Response:

JSPG0003E: jsp:param has invalid parent tag
Explanation:
User Response:

JSPG0004E: jsp:param name attribute cannot be empty
Explanation:
User Response:

JSPG0005E: tld file could not be found for uri[{0}] prefix [{1}]
Explanation:
User Response:

JSPG0006E: Custom Tag is missing required attribute {0}
Explanation:
User Response:

JSPG0007E: Custom Tag has missing attribute {0}
Explanation:
User Response:

JSPG0008E: Custom Tag has invalid attributes
Explanation:
User Response:

JSPG0009E: Unable to load tag handler class {0}
Explanation:
User Response:

JSPG0010E: jsp:root element has no attributes
Explanation:
User Response:

JSPG0011E: jsp:useBean is missing an id attribute
Explanation:
User Response:

JSPG0012E: jsp:useBean is missing a type attribute or class attribute
Explanation:
User Response:

JSPG0013E: A bean with id {0} has already been defined
Explanation:
User Response:

JSPG0014E: scope attribute cannot be "session" if session page directive is false
Explanation:
User Response:

JSPG0015E: jsp:useBean cannot have both a class and a beanName attribute (class = [{0}] beanName =[{1}]).
Explanation:
User Response:

JSPG0016E: invalid scope attribute value. Must page, request, session or application. Scope specified {0}.
Explanation:
User Response:

JSPG0017E: jsp:useBean contains no attributes
Explanation:
User Response:

JSPG0018E: Expression contains no text
Explanation:
User Response:

JSPG0019E: Invalid value for session directive
Explanation:
User Response:

JSPG0020E: Invalid value for buffer directive
Explanation:
User Response:

JSPG0021E: Invalid value for autoflush directive
Explanation:
User Response:

JSPG0022E: Invalid value for threadsafe directive
Explanation:
User Response:

JSPG0023E: Invalid value for iserrorpage directive
Explanation:
User Response:

JSPG0024E: Unknown directive {0}
Explanation:
User Response:

JSPG0025E: Page directive contains no attributes
Explanation:
User Response:

JSPG0026E: Scriptlet contains no text
Explanation:
User Response:

JSPG0027E: Declaration contains no text
Explanation:
User Response:

JSPG0028E: jsp:text contains no text
Explanation:
User Response:

JSPG0029E: invoke action can only be used in tag files
Explanation:
User Response:

JSPG0030E: doBody action can only be used in tag files
Explanation:
User Response:

JSPG0031E: tag directive can only be used in tag files
Explanation:
User Response:

JSPG0032E: attribute directive can only be used in tag files
Explanation:
User Response:

JSPG0033E: variable directive can only be used in tag files
Explanation:
User Response:

JSPG0034E: xml dtd or schema not found
Explanation:
User Response:

JSPG0035E: page encoding in jsp configuration does not match one in jsp
Explanation:
User Response:

JSPG0036E: Failed to find resource {0}
Explanation:
User Response:

JSPG0037E: Invalid value for isErrorPage directive
Explanation:
User Response:

JSPG0038E: Invalid value for dynamicAttributes directive
Explanation:
User Response:

JSPG0039E: page directive can only be used in page files
Explanation:
User Response:

JSPG0040E: {0} has already been statically included
Explanation:
User Response:

JSPG0041E: Expression language function class not found. {0} {1} {2}
Explanation:
User Response:

JSPG0042E: Parenthesis expected for expression language function {0} {1}
Explanation:
User Response:

JSPG0043E: Invalid signature for expression language function {0} {1}
Explanation:
User Response:

JSPG0044E: Comma expected for expression language function {0} {1}
Explanation:
User Response:

JSPG0045E: Error while retrieving bean information for {0}
Explanation:
User Response:

JSPG0046E: Unable to locate tagfile for tag {0}
Explanation:
User Response:

JSPG0047E: Unable to locate tag library for uri {0}
Explanation:
User Response:

JSPG0048E: Page failed to validate using taglib validator for {0} : {1}
Explanation:
User Response:

JSPG0049E: {0} failed to compile : {1}
Explanation:
User Response:

JSPG0050E: tld file could not be found at location {0}
Explanation:
User Response:

JSPG0051E: Duplicate Page Directive value : {0}
Explanation:
User Response:

JSPG0052E: Duplicate Tag Directive value : {0}
Explanation:
User Response:

JSPG0053E: Include preludes are not allowed in Jsp Documents
Explanation:
User Response:

JSPG0054E: Include codas are not allowed in Jsp Documents
Explanation:
User Response:

JSPG0055E: Unable to create an xml attribute from name [{0}] value [{1}]
Explanation:
User Response:

JSPG0056E: Unable to create an xml element from namespace [{0}] name [{1}]
Explanation:
User Response:

JSPG0057I: JspModC -appDir -tmpDir -forceTranslation -additionalClasspath -jspFile
Explanation:
User Response:

JSPG0058I: IBM JSP 2.0 Engine
Explanation:
User Response:

JSPG0060E: Invalid jsp syntax [{0}]
Explanation:
User Response:

JSPG0061E: Attribute {0} is unrecognised for jsp element {1}
Explanation:
User Response:

JSPG0062E: Request-time Attribute {0} is unrecognised for jsp element {1}
Explanation:
User Response:

JSPG0063E: Invalid value for language directive {0}
Explanation:
User Response:

JSPG0064E: Invalid value for buffer directive valid values. If value other than none, suffix kb is required
Explanation:
User Response:

JSPG0065E: Illegal use of EL tag. Nesting of EL tags are not permitted
Explanation:
User Response:

JSPG0066E: Failed to parse Expression Language tag {0}
Explanation:
User Response:

JSPG0067E: Illegal use of EL Tag. Value "{2}" is not permitted for attribute "{1}" for jsp element {0}
Explanation:
User Response:

JSPG0068E: Unmatched tag found while parsing jsp [{0}]
Explanation:
User Response:

JSPG0069E: Unmatched end tag found while parsing jsp. Expecting {0} found {1} at {2}
Explanation:
User Response:

JSPG0070E: Duplicate url pattern [{0}] found in the Web Applications Jsp Configuration
Explanation:
User Response:

JSPG0071E: Failed to load tld from webinf resource {0} msg: {1}
Explanation:
User Response:

JSPG0072E: Failed to load tld from jar {0} resource {1} msg: {2}
Explanation:
User Response:

JSPG0073E: useBean class "{0}" must be assignable to type "{1}" for jsp element {2}
Explanation:
User Response:

JSPG0074E: Cannot locate class to determine if useBean class "{0}" is assignable to type "{1}" for jsp element {2}
Explanation:
User Response:

JSPG0075E: Multiple occurences of attribute {0} not permitted for jsp element {1}
Explanation:
User Response:

JSPG0076E: Missing required attribute {0} for jsp element {1}
Explanation:
User Response:

JSPG0077E: End of file reached while processing {0} at {1}
Explanation:
User Response:

JSPG0078E: Invalid value for tag directive attribute body-content. value {0}
Explanation:
User Response:

JSPG0079E: Multiple occurrences of attribute name or alias or name-given {2} not permitted. {2} specified in jsp elements "{0}" and "{1}"
Explanation:
User Response:

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:
User Response:

JSPG0081E: Tag file variable directive requires either a name-given or name-from-attribute attribute for jsp element {0}.
Explanation:
User Response:

JSPG0082E: Invalid value for variable directive attribute scope "{1}" jsp element {0}.
Explanation:
User Response:

JSPG0083E: Missing required atribute alias when name-from-attribute "{1}" specified jsp element {0}
Explanation:
User Response:

JSPG0084E: Attribute alias "{2}" not permitted if name-given "{1}" specified. jsp element {0}
Explanation:
User Response:

JSPG0085E: Error while load class specified for tag attibute for {0}
Explanation:
User Response:

JSPG0086E: Static Include {0} must be of the same type as the including jsp.
Explanation:
User Response:

JSPG0087E: Mismatch found between jsp config encoding {0} and xml prolog encoding {1}
Explanation:
User Response:

JSPG0088E: Mismatch found between jsp config encoding {0} and page directive encoding {1}
Explanation:
User Response:

JSPG0089E: Mismatch found between page directive encoding {0} and xml prolog encoding {1}
Explanation:
User Response:

JSPG0090E: Error pageEncoding has already been supplied for this jsp
Explanation:
User Response:

JSPG0091E: An error occurred at line: {0} in the file: {1}
Explanation:
User Response:

JSPG0092E: An error occurred between lines: {0} and {1} in the file: {2}
Explanation:
User Response:

JSPG0093E: Generated servlet error from file: {0}
Explanation:
User Response:

JSPG0094E: Unable to locate the prefix for el function {0}
Explanation:
User Response:

JSPG0095E: Unable to locate the el function {0} in the tld with uri {1}
Explanation:
User Response:

JSPG0096E: Failed to load {0}
Explanation:
User Response:

JSPG0097E: Failed to load el function method {0}
Explanation:
User Response:

JSPG0098E: jsp:output tag cannot have a body
Explanation:
User Response:

JSPG0099E: jsp:root version attribute is invalid : {0}
Explanation:
User Response:

JSPG0100E: Name of Dynamic Attributes Map is the same as the tag attribute directive name attribute
Explanation:
User Response:

JSPG0101E: Name of Dynamic Attributes Map is the same as the tag varibke directive name-given attribute
Explanation:
User Response:

JSPG0102E: jsp:text cannot have child elements
Explanation:
User Response:

JSPG0105E: The {0} tag can only have jsp:attribute in its body. Found: {1}
Explanation:
User Response:

JSPG0106E: The jsp:output element can only be used in JSP documents and in tag files in XML syntax.
Explanation:
User Response:

JSPG0107E: The jsp:attribute element with value of type JspFragment cannot contain scriptlets {0}.
Explanation:
User Response:

JSPG0108E: Illegal to specify rtexprvalue for attribute of type fragment. rtexprvalue: {0}
Explanation:
User Response:

JSPG0109E: Illegal to specify type for attribute of type fragment. type: {0}
Explanation:
User Response:

JSPG0110E: Illegal to specify type as primitive Class for tag file attribute. primitive {0}
Explanation:
User Response:

JSPG0111E: Unable to verify tag file attribute type {0} is not a primitive Class.
Explanation:
User Response:

JSPG0112E: Scripting in runtime expressions disabled for this translation unit.
Explanation:
User Response:

JSPG0113E: Scriptlets disabled for this translation unit.
Explanation:
User Response:

JSPG0114E: Declarations disabled for this translation unit.
Explanation:
User Response:

JSPG0115E: Expressions disabled for this translation unit.
Explanation:
User Response:

JSPG0116E: Illegal to specify page directive {0} more than once if they have different values. first: {1} second: {2}
Explanation:
User Response:

JSPG0117E: Illegal to specify uri in conjunction with tagdir in taglib directive. uri: "[{0}]" tagdir: "[{1}]"
Explanation:
User Response:

JSPG0118E: Illegal to specify multiple occurrences of uri in taglib directive. uri: "[{0}]" uri: "[{1}]"
Explanation:
User Response:

JSPG0119E: Illegal to specify multiple occurrences of tagdir in taglib directive. tagdir: "[{0}]" tagdir: "[{1}]"
Explanation:
User Response:

JSPG0120E: Illegal to specify different values for pageEncoding attribute and configuration element for matching URI pattern. directive: "[{0}]" configuration: "[{1}]"
Explanation:
User Response:

JSPG0121E: Illegal to use to define the value of an attribute of
Explanation:
User Response:

JSPG0122E: Unable to parse EL function {0}.
Explanation:
User Response:

JSPG0123E: Unable to locate tag attribute info for tag attribute {0}.
Explanation:
User Response:

JSPG0124E: Custom tag attribute {0} cannot be runtime expression. value: "[{1}]"
Explanation:
User Response:

JSPG0125E: Custom tag attribute {0} cannot be runtime fragment.
Explanation:
User Response:

JSPG0126E: jsp {0} cannot contain more than one pageEncoding directive
Explanation:
User Response:

JSPG0127E: Illegal to specify tag directive {0} more than once. first: {1} second: {2}
Explanation:
User Response:

JSPG0128E: Unable to translate JSP {0}.
Explanation:
User Response:

JSPG0129E: JspServlet failed to initialize
Explanation:
User Response:

JSPG0130E: Invalid value for the flush attribute: {0}
Explanation:
User Response:

JSPG0131E: Error non-null tei and variable subelements found
Explanation:
User Response:

JSPG0132E: Invalid Attributes found for {0} {1}. Error is {2}
Explanation:
User Response:

JSPG0133E: Parent of jsp:attribute must be either a standard or custom action
Explanation:
User Response:

JSPG0134E: Parent of jsp:body is invalid
Explanation:
User Response:

JSPG0135E: Parent of jsp:body is is a custom tag that has specified it has no body in its tld
Explanation:
User Response:

JSPG0136E: jsp:invoke cannot have both var and varReader set
Explanation:
User Response:

JSPG0137E: jsp:doBody cannot have both var and varReader set
Explanation:
User Response:

JSPG0138E: jsp:invoke must have either var and varReader set when scope is set
Explanation:
User Response:

JSPG0139E: jsp:doBody must have either var and varReader set when scope is set
Explanation:
User Response:

JSPG0140E: jsp:invoke scope value is invalid
Explanation:
User Response:

JSPG0141E: jsp:doBody scope value is invalid
Explanation:
User Response:

JSPG0142E: Runtime Expr Value "{2}" is not permitted for attribute "{1}" for jsp element {0}
Explanation:
User Response:

JSPG0143E: name attribute of jsp:attribute has different prefix to parent : {0} not equal {1}
Explanation:
User Response:

JSPG0144E: Invalid value for plugin "type" attribute : {0}
Explanation:
User Response:

JSPG0145E: Unknown JSP element : {0}
Explanation:
User Response:

JSPG0146E: Invalid attribute for include directive : {0}
Explanation:
User Response:

JSPG0147E: Missing required attribute "file" for include directive.
Explanation:
User Response:

JSPG0148E: JSP file does not exist: {0}
Explanation:
User Response:

JSPG0149E: Target directory does not exist: {0}
Explanation:
User Response:

JSPG0150E: Target directory name is not a directory: {0}
Explanation:
User Response:

JSPG0151I: Return code: {0}
Explanation:
User Response:

JSPG0152E: Unable to create classloader.
Explanation:
User Response:

JSPG0153I: Initializing server...
Explanation:
User Response:

JSPG0154E: Exception caught while processing command-line arguments.
Explanation:
User Response:

JSPG0155E: Unknown command-line argument: {0}
Explanation:
User Response:

JSPG0156W: Unknown log level {0}, using default {1}
Explanation:
User Response:

JSPG0157I: Cell name not supplied; using default: {0}
Explanation:
User Response:

JSPG0158I: Node name not supplied; using default: {0}
Explanation:
User Response:

JSPG0159I: Server name not supplied; using default: {0}
Explanation:
User Response:

JSPG0160I: Compiling all webmodules
Explanation:
User Response:

JSPG0161E: Unable to initialize server.
Explanation:
User Response:

JSPG0162E: Exception caught while adding ComponentManager service.
Explanation:
User Response:

JSPG0163E: Exception caught while initializing batch compiler service.
Explanation:
User Response:

JSPG0164E: Repository service not available.
Explanation:
User Response:

JSPG0165I: Reading config file...
Explanation:
User Response:

JSPG0166E: Enterprise Application not found: {0}
Explanation:
User Response:

JSPG0167I: Finished reading config file.
Explanation:
User Response:

JSPG0168I: The Batch Compiler exited successfully without errors.
Explanation:
User Response:

JSPG0169I: The Batch Compiler exited with errors.
Explanation:
User Response:

JSPG0170E: Error reading configuration: {0} {1}
Explanation:
User Response:

JSPG0171E: Error while finding Server.
Explanation:
User Response:

JSPG0172E: Error while finding enterprise app.
Explanation:
User Response:

JSPG0173E: extractToDir directory is not writable: {0}
Explanation:
User Response:

JSPG0174E: extractToDir directory is not a directory: {0}
Explanation:
User Response:

JSPG0175E: Exception caught while extracting earfile {0}.
Explanation:
User Response:

JSPG0176E: WAR path does not exist: {0}
Explanation:
User Response:

JSPG0177E: WAR path is not a file: {0}
Explanation:
User Response:

JSPG0178E: EAR path does not exist: {0}
Explanation:
User Response:

JSPG0179E: EAR path is not a file: {0}
Explanation:
User Response:

JSPG0180E: Webmodule not found: {0}
Explanation:
User Response:

JSPG0183I: Removing {0}
Explanation:
User Response:

JSPG0184I: Extracting {0} to {1}
Explanation:
User Response:

JSPG0185I: Done extracting.
Explanation:
User Response:

JSPG0186I: Saving {0}
Explanation:
User Response:

JSPG0187I: Done saving.
Explanation:
User Response:

JSPG0188E: Exception encountered during save operation.
Explanation:
User Response:

JSPG0192E: No EAR path or WAR path or Enterpise App name was given. Must supply one of these.
Explanation:
User Response:

JSPG0193E: Must supply only one of EAR path or WAR path or Enterprise App.
Explanation:
User Response:

JSPG0194W: Webmodule name {0} being ignored because WAR path was given.
Explanation:
User Response:

JSPG0195E: Exception caught while extracting warfile: {0}.
Explanation:
User Response:

JSPG0196E: JSP Batch Compiler extractToDir must not overlap with ear path.
Explanation:
User Response:

JSPG0197E: JSP Batch Compiler extractToDir must not overlap with war path.
Explanation:
User Response:

JSPG0198E: extractToDir does not exist: {0}
Explanation:
User Response:

JSPG0199E: Exception caught getting warfile list
Explanation:
User Response:

JSPG0200E: Exception caught opening earfile
Explanation:
User Response:

JSPG0202E: Exception caught opening warfile
Explanation:
User Response:

JSPG0203W: ExtractToDir {0} being ignored because enterpriseapp.name was given.
Explanation:
User Response:

JSPG0204W: Exception caught when adding variable map. {0}
Explanation:
User Response:

JSPG0205W: Error creating order of JSP visitors. {0}
Explanation:
User Response:

JSPG0206E: Error loading jsp-visitor-definition
Explanation:
User Response:

JSPG0207E: Exception caught while processing command-line arguments: File: {0} Message: {1}
Explanation:
User Response:

JSPG0208W: compileToWebInf being ignored because compileToDir {0} was given.
Explanation:
User Response:

JSPG0209E: {0}(0,0) failed to read JSP: {1}
Explanation:
User Response:

JSPG0210E: autoFlush cannot be set to false when buffer is set to none
Explanation:
User Response:

JSPG0211E: jsp:root must be top element in document
Explanation:
User Response:

JSPG0212E: jsp:root can only be used in JSP Documents
Explanation:
User Response:

JSPG0213E: Error must provide a doctype-root-element when using doctype-system attribute
Explanation:
User Response:

JSPG0214E: Error doctype-system is not provided.
Explanation:
User Response:

JSPG0215E: Error failed to create configured translation context from {0}. Exception : {2}
Explanation:
User Response:

JSPG0216E: Error failed to load configured context class {0}
Explanation:
User Response:

JSPG0217E: Error failed to load configured extension processor class {0}
Explanation:
User Response:

JSPG0218E: Error failed to locate setter method for attribute {1} in tag class {0}
Explanation:
User Response:

JSPG0219E: Error taglib directive attribute {0} with value {1} is unknown.
Explanation:
User Response:

JSPG0220E: Error taglib directive missing required attribute prefix.
Explanation:
User Response:

JSPG0221E: Compiling a JSP in META-INF not allowed. File: {0}
Explanation:
User Response:

JSPG0222E: If removeTempDir is true, enterpriseApp.name must be given.
Explanation:
User Response:

JSPG0223E: If translate is false, removeTempDir must be true.
Explanation:
User Response:

JSPG0224W: JSP Engine parameter scratchdir [{0}] is being ignored because ear.path or war.path was given.
Explanation:
User Response:

JSPG0225E: An error occurred at line: {0} in the statically included file: {1}
Explanation:
User Response:

JSPG0226E: An error occurred between lines: {0} and {1} in the statically included file: {2}
Explanation:
User Response:

JSPG0227E: Exception caught while translating {0}
Explanation:
User Response:

JSPG0228E: Exception caught while translating {0}: error in statically included file {1}
Explanation:
User Response:

JSPG0233E: Exception caught while getting configuration options.
Explanation:
User Response:

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.
User Response: 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).
User Response: 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).
User Response: Verify that the TagLibraryValidator class exists and is accessible to this Web module.