[jboss-jira] [JBoss JIRA] (AS7-630) Can't process JSF TLD
Hendy Irawan (JIRA)
jira-events at lists.jboss.org
Thu Feb 16 04:16:39 EST 2012
[ https://issues.jboss.org/browse/AS7-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667011#comment-12667011 ]
Hendy Irawan commented on AS7-630:
----------------------------------
The error message needs to be much improved, it should inform which file and line number the error occurs.
Trying to deploy JasperReports Server 4.5 on JBoss 7.1.0.CR1b, I'm blind as to which file is the trouble:
{code}
16:11:26,817 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-15) MSC00001: Failed to start service jboss.deployment.unit."jasperserver.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver.war".PARSE: Failed to process phase PARSE of deployment "jasperserver.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_23]
Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.metadata.web.spec.BodyContentType.EMPTY
at java.lang.Enum.valueOf(Enum.java:214) [:1.6.0_23]
at org.jboss.metadata.web.spec.BodyContentType.valueOf(BodyContentType.java:30)
at org.jboss.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataParser.java:117)
at org.jboss.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataParser.java:226)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:124)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:105)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
Is body-content values really case sensitive?
Even if it is, it should only generate a WARN, not ERROR.
If JBoss decides to have a "strict mode", it should come with strict mode disabled by default. Strict mode can be enabled during development to squash typo bugs etc. but in deployment it should be disabled by default, especially to run legacy webapps.
> Can't process JSF TLD
> ---------------------
>
> Key: AS7-630
> URL: https://issues.jboss.org/browse/AS7-630
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.0.0.Alpha1
> Reporter: Stan Silvert
> Assignee: Remy Maucherat
> Attachments: mojarra2.0-bundled.war
>
>
> WAR to reproduce is attached.
> 15:32:07,764 ERROR [org.jboss.as.server.deployment] (pool-3-thread-1) Caught exc
> eption handling update (param is 10cd5140-b773-49da-97ab-0fb055b56141): java.lan
> g.RuntimeException: Failed to process deployment chain.
> at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe
> ploymentStartStopHandler.java:203)
> at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl
> oymentStartStopHandler.java:87)
> at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl
> oymentStartStopHandler.java:71)
> at org.jboss.as.model.ServerDeploymentStartStopHandler.redeploy(ServerDe
> ploymentStartStopHandler.java:117)
> at org.jboss.as.model.ServerModelDeploymentFullReplaceUpdate.applyUpdate
> (ServerModelDeploymentFullReplaceUpdate.java:68)
> at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl
> e.applyUpdate(ServerUpdateController.java:430)
> at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl
> e.access$200(ServerUpdateController.java:400)
> at org.jboss.as.server.mgmt.ServerUpdateController.applyUpdates(ServerUp
> dateController.java:189)
> at org.jboss.as.server.mgmt.ServerUpdateController.executeUpdates(Server
> UpdateController.java:142)
> at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl$2.run
> (ServerDeploymentManagerImpl.java:218)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886) [:1.6.0_18]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908) [:1.6.0_18]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_18]
> Caused by: org.jboss.as.deployment.unit.DeploymentUnitProcessingException: Faile
> d to parse "/C:/projects/as7trunk/jboss-as/build/target/jboss-7.0.0.Alpha2/bin/c
> ontent/mojarra2.0-bundled.war/WEB-INF/lib/jsf-impl-2.0.3-b05.jar/META-INF/html_b
> asic.tld"
> at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl
> dParsingDeploymentProcessor.java:118)
> at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds
> (TldParsingDeploymentProcessor.java:97)
> at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processDepl
> oyment(TldParsingDeploymentProcessor.java:77)
> at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(D
> eploymentChainImpl.java:50)
> at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe
> ploymentStartStopHandler.java:201)
> ... 12 more
> Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.met
> adata.web.spec.BodyContentType.
> JSP
> at java.lang.Enum.valueOf(Enum.java:196) [:1.6.0_18]
> at org.jboss.metadata.web.spec.BodyContentType.valueOf(BodyContentType.j
> ava:32)
> at org.jboss.as.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataP
> arser.java:111)
> at org.jboss.as.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataP
> arser.java:200)
> at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl
> dParsingDeploymentProcessor.java:116)
> ... 16 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list