4 Replies Latest reply on Apr 28, 2015 8:17 PM by lylewang

JBAS018014: Failed to parse XML descriptor

sharmamanish3 Apr 23, 2015 10:58 AM

Hi,

I am migrating an application from Glassfish 2.1 (already in production with no issues) to JBOSS 6.4 GA version (development mode).

I encountered below error:

JBAS018014: Failed to parse XML descriptor

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]

[Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45]

[Server:server-one] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]

[Server:server-one] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/C:/Program Files/J

BOSSEap/content/ARP3.ear/ARP3.war/WEB-INF/lib/f1jtaglib.jar/META-INF/f1taglib.tld" at [3,2]

[Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]

[Server:server-two] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]

[Server:server-one] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:143)

[Server:server-one] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:122)

[Server:server-two] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/C:/Program Files/J

BOSSEap/content/ARP3.ear/ARP3.war/WEB-INF/lib/f1jtaglib.jar/META-INF/f1taglib.tld" at [3,2]

[Server:server-one] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:84)

[Server:server-two] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:143)

[Server:server-one] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-red

hat-21.jar:7.5.0.Final-redhat-21]

[Server:server-two] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:122)

[Server:server-two] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:84)

[Server:server-two] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-red

hat-21.jar:7.5.0.Final-redhat-21]

[Server:server-one] ... 5 more

[Server:server-two] ... 5 more

[Server:server-one] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,2]

[Server:server-two] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,2]

[Server:server-one] Message: Unexpected element 'tlibversion' encountered

[Server:server-two] Message: Unexpected element 'tlibversion' encountered

[Server:server-one] at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)

[Server:server-two] at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)

[Server:server-one] at org.jboss.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataParser.java:146)

[Server:server-two] at org.jboss.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataParser.java:146)

[Server:server-one] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:141)

[Server:server-two] at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:141)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am attaching the file f1taglib.tld file which was part of standard jar f1jtaglib.jar file.

The MANIFEST.MF file of this jar have content

------------------------------------------------------------------------------------------------------------------------------

Manifest-Version: 1.0

Ant-Version: Apache Ant 1.6.1

Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)

Name: com/f1j/swing/JBook.class

Java-Bean: True

---------------------------------------------------------------------------------------------------------

Thanks in advance for any help on above.

Regards,

Manish Sharma

f1taglib - Copy.tld.zip 5.8 KB

1. Re: JBAS018014: Failed to parse XML descriptor

sharmamanish3 Apr 24, 2015 11:37 AM (in response to sharmamanish3)

Any experts to help on above please. I a still looking into this with no luck.
Actions
2. Re: JBAS018014: Failed to parse XML descriptor

lylewang Apr 27, 2015 2:32 AM (in response to sharmamanish3)

Unexpected element 'tlibversion' encountered
Checking your tld file it doesn't specify the schema.

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

<taglib>

<tlibversion>11.0.1.5</tlibversion>

<jspversion>1.1</jspversion>

Maybe try to specify the schema file using "DOCTYPE", or like this: http://stackoverflow.com/questions/8260253/correct-tld-file-header
Just like in the tld file you do in the other thread: JBAS018014: Failed to parse XML descriptor "...ARP3.war/WEB-INF/lib/taglibs-xtags.jar/META-INF/taglib.tld
Actions
3. Re: JBAS018014: Failed to parse XML descriptor

sharmamanish3 Apr 28, 2015 10:51 AM (in response to lylewang)

Many thanks Lee. I added but again it failed because it is a third party TLD file containing Elements which don't confirm to the original sun DTD.
I am thinking - is it possible to suppress the TLD validations somehow for JBOSS.
We never faced this issue on glassfish so I think glassfish doesn't validate the TLDs initially whereas JBOSS does causing failure.
Actions
4. Re: JBAS018014: Failed to parse XML descriptor

lylewang Apr 28, 2015 8:17 PM (in response to sharmamanish3)

Source code see here: http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.metadata/jboss-metadata-web/7.2.1.Final/org/jboss/metadata/parser/jsp/TldMetaDataParser.java#TldMetaDataParser.parse%28javax.xml.stream.XMLStreamReader%29

Didn't see any configuration item to suppress the validation so I don't think there is a way.

However your Tag Lib .tld file should (must, actually) confirm to a schema.
The correct way should be getting a schema compliant tld file, rather than suppressing the validation (even if you could do that, the tag lib wouldn't likely work as expected...)

check this blog: Validate your Tag Library Descriptor files! (Jan Luehe's Blog)
Actions

Go to original post