[jboss-jira] [JBoss JIRA] (AS7-2626) Trailing forgotten --> does not generate a good error message on host.xml

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-2626:
----------------------------------

    Assignee:     (was: Brian Stansberry)

    
> Trailing forgotten --> does not generate a good error message on host.xml
> -------------------------------------------------------------------------
>
>                 Key: AS7-2626
>                 URL: https://issues.jboss.org/browse/AS7-2626
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Jim Tyrrell
>              Labels: eap6-ux
>
> This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line...
>     <domain-controller>
>        <!--<local/>-->
>        <!-- Alternative remote domain controller configuration with a host and$
>        <remote host="127.0.0.1" port="9999"/>-->
>     </domain-controller>
> Generates this error message:
> [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> Several lines further down...you get this message...
> [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag().
> [Host Controller]  at [row,col {unknown-source}]: [44,4]
> It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line.
> Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4.  More verbosity would be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira