Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6670

VDX - pretty print does not provide 'Elements allowed here are: ' when element is not terminated by the matching end-tag

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR8
    • 7.1.0.DR7
    • Server
    • None

      VDX - pretty print does not kick in when element has no value

      • open standalone.xml
      • locate webservices subsystem
      • add <foo /> under <wsdl-host>...</wsdl-host>
      • run standalone.sh
      • check log to see 'Elements allowed here are:'
      • replace <foo /> with <mmodify-wsdl-address>true</modify-wsdl-address>
      • run standalone.sh
      • check log, no 'Elements allowed here are:' is present

      <foo /> error:

      12:15:18,242 ERROR [org.jboss.as.controller] (Controller Boot Thread) 
      
      OPVDX001: Validation error in standalone-rs.xml ================================
      
        382: <!--            <mmodify-wsdl-address>true</modify-wsdl-address>
        383: -->
        384: <foo/>
             ^^^^ 'foo' isn't an allowed element here
                  Elements allowed here are: 
                  - client-config
                  - endpoint-config
                  - modify-wsdl-address
                  - wsdl-host
                  - wsdl-path-rewrite-rule
                  - wsdl-port
                  - wsdl-secure-port
                  - wsdl-uri-scheme
      
        385:             <endpoint-config name="Standard-Endpoint-Config"/>
        386:             <endpoint-config name="Recording-Endpoint-Config">
        387:                 <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
      
       The underlying error message was:
       > ParseError at [row,col]:[384,1]
       > Message: WFLYCTL0198: Unexpected element '{urn:jboss:domain:webservices:2.0}foo' encountered
      

      <mmodify-wsdl-address>true</mmodify-wsdl-address> error:

      12:26:07,023 ERROR [stderr] (Controller Boot Thread) [Fatal Error] :386:29: The element type "mmodify-wsdl-address" must be terminated by the matching end-tag "</mmodify-wsdl-address>".
      12:26:07,039 ERROR [org.jboss.as.controller] (Controller Boot Thread) 
      
      OPVDX001: Validation error in standalone-rs.xml ================================
      
        384: <!-- <mmodify-wsdl-address>true</mmodify-wsdl-address>
        385: -->
        386: <mmodify-wsdl-address>true</modify-wsdl-address>
             ^^^^ 'mmodify-wsdl-address' isn't an allowed element here
      
        387:             <endpoint-config name="Standard-Endpoint-Config"/>
        388:             <endpoint-config name="Recording-Endpoint-Config">
        389:                 <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
      
       The underlying error message was:
       > ParseError at [row,col]:[386,1]
       > Message: WFLYCTL0198: Unexpected element '{urn:jboss:domain:webservices:2.0}mmodify-wsdl-address' encountered
      
      ================================================================================
      
      
      12:26:07,041 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
      	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
      	at org.jboss.as.server.ServerService.boot(ServerService.java:355)
      	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
      	at java.lang.Thread.run(Thread.java:745)
      

              tcrawley Toby Crawley (Inactive)
              rsvoboda@redhat.com Rostislav Svoboda
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: