Validation error parsing TLD using web-jsptaglibrary_1_1.dtd

[Former Member]

Does SAP EE 5 not support older versions of tag libraries? It was my understanding that descriptors defined by previous versions of the Java EE specification must be supported. This does work on several other application servers as well.

I am receiving a validation error trying to deploy a tld that uses web-jsptaglibrary_1_1.dtd (This is from J2EE 1.2 - JSP 1.1 Tag Library DTD). It seems to be trying to validate against a schema (J2EE 1.4 or higher when the descriptors started being validated by schemas?). Below is a snippet of my taglib:

<?xml version="1.0" encoding="ISO-8859-1" ?>

<!DOCTYPE taglib

PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"

"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">

<taglib>

<tlibversion>1.0</tlibversion>

<jspversion>1.1</jspversion>

<shortname></shortname>

And here is a snippet of the error I'm receiving:

Error in parsing [turtle.tld] TLD file. The error is: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: org.xml.sax.SAXParseException: Validation error : line: 6; col: 5; :tag : Element is not allowed. Expected children elements : [:short-name].(:main:, row=6, col=5) -> org.xml.sax.SAXParseException: Validation error : line: 6; col: 5; :tag : Element is not allowed. Expected children elements : [:short-name].

at com.sap.engine.lib.schema.validator.SchemaDocHandler.collectError(SchemaDocHandler.java:902)

at com.sap.engine.lib.schema.validator.SchemaDocHandler.collectError(SchemaDocHandler.java:896)

at com.sap.engine.lib.schema.validator.SchemaDocHandler.initElementXPathStep_Error(SchemaDocHandler.java:524)

at com.sap.engine.lib.schema.validator.SchemaDocHandler.startElementEnd(SchemaDocHandler.java:284)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1821)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2449)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1848)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2852)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parse_SchemaValidation(Parser.java:241)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:288)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:173)

at com.sap.engine.lib.processor.SchemaProcessor.parse(SchemaProcessor.java:197)

at com.sap.engine.services.servlets_jsp.server.deploy.descriptor.TagLibDescriptor.loadDescriptorFromStream(TagLibDescriptor.java:90)

at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.processTld(ApplicationThreadInitializer.java:426)

Maybe there is some configuration that I need to setup to get this working?

[former_member185706 · Accepted solution]

I'd suggest to put a vallue of <shortname> tag i.e. :

<shortname>myTag</shortname>

[Former Member]

That solved the problem. It does not seem to like an empty value for the <shortname> element.

Thanks Bojidar!