Validation error in Tag Library at deploy time

Question

I am trying to deploy a JSF2 app to NW CE 7.1 EHP1. This application deploy's fine to Tomcat. When I deploy to SAP it gives an error: Error in parsing [META-INF/primefaces-i.tld] TLD file in the following [D:\usr\sap\NCX\J00\j2ee\cluster\apps\com.sap\IDMear\servlet_jsp\IDM\root\WEB-INF\lib\primefaces-1.0.0.jar] JAR file.
[EXCEPTION]
com.sap.engine.lib.xml.parser.NestedSAXParseException: Fatal Error: org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.(:main:, row=13, col=17) -> org.xml.sax.SAXParseException: Validation error : line: 13; col: 16; :description : Element is not allowed.
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:140)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:174)
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)
From looking at the TLD XSD for JEE 5, the Description field should be allowed. Do you know why it is not comparing the TLD against the correct schema or if there is another explanation?
This is a 3rd party faces component library. Here is where it fails:
<?xml version="1.0" encoding="UTF-8"?>
<taglib xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.1">
     <tlib-version>1.2</tlib-version>
     <short-name>i</short-name>
     <uri>http://primefaces.prime.com.tr/touch</uri>
     <tag>
          <name>application</name>
          <tag-class>org.primefaces.touch.component.application.ApplicationTag</tag-class>
          <body-content>JSP</body-content>
          <attribute>
               <name>id</name>
               <required>false</required>
               <description><![CDATA[Id of the component]]></description>               <rtexprvalue>false</rtexprvalue>
          </attribute>
Any suggestions would be appreciated.

Answer 1

It looks like the 3rd party tld did not have the description in the correct order. It has been corrected in a new build.