[
https://issues.jboss.org/browse/JBMETA-377?page=com.atlassian.jira.plugin...
]
Jay Kumar SenSharma commented on JBMETA-377:
--------------------------------------------
Sent a new Pull request for this issue:
https://github.com/jboss/metadata/pull/65
With this fix it should report the actual cause of the deployment failure as following:
{code}
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[16,7]
Message: <param-name> is not defined properly inside the web.xml
at
org.jboss.metadata.parser.ee.ParamValueMetaDataParser.parse(ParamValueMetaDataParser.java:90)
at
org.jboss.metadata.parser.servlet.WebCommonMetaDataParser.parse(WebCommonMetaDataParser.java:70)
at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:184)
at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:57)
{code}
NullPointerException occurs during parsing web.xml with missing
context param-name
----------------------------------------------------------------------------------
Key: JBMETA-377
URL:
https://issues.jboss.org/browse/JBMETA-377
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: common
Affects Versions: 8.0.0.Final
Reporter: Jay Kumar SenSharma
[Opening this issue to track down the issue specific to jboss metadata]
While deploying a WAR, If the web.xml file is used which has context <param-value>
defined, However it has missing <param-name> then it causes NullPointerException.
Refer to for more details:
https://issues.jboss.org/browse/WFLY-3699
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)