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

Pretty-printing XML validation - do not truncate list of possible allowed elements

XMLWordPrintable

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

      If name of attribute contains typo then all possible options should be provided and list should not be truncated like in example below where is typo in <in-vm-acceptator in messaging-activemq subsystem.

      Example:

      09:21:26,936 ERROR [org.jboss.as.controller] (Controller Boot Thread) 
      OPVDX001: Validation error in standalone-full-ha.xml ===========================
        393:     <param name="use-nio" value="true"/>
        394: </remote-acceptor>
        395: <in-vm-accepator name="in-vm" server-id="0"/>
             ^^^^ 'in-vm-accepator' isn't an allowed element here
                  Elements allowed here are: 
                  - acceptor
                  - address-setting
                  - bindings-directory
                  - bridge
                  - broadcast-group
                  - cluster-connection
                  - connection-factory
                  - connector
                  - connector-service
                  - discovery-group
                  (and 24 more)
                  
                  Did you mean 'in-vm-acceptor'?
      
        396: <broadcast-group name="bg-group1" jgroups-channel="activemq-cluster" broadcast-period="1000" connectors="netty"/>
        397: <discovery-group name="dg-group1" jgroups-channel="activemq-cluster" refresh-timeout="1000"/>
        398: <cluster-connection name="my-cluster" address="jms" connector-name="netty" retry-interval="1000" discovery-group="dg-group1"/>
      
       The underlying error message was:
       > ParseError at [row,col]:[395,17]
       > Message: WFLYCTL0377: Unexpected element '{urn:jboss:domain:messaging-activemq:1.1}in-vm-accepator' encountered. Valid elements are: 'replication-master, shared-store-master, connector-service, http-acceptor, broadcast-group, cluster-connection, bindings-directory, replication-slave, shared-store-slave, shared-store-colocated, live-only, address-setting, jms-queue, pooled-connection-factory, large-messages-directory, divert, journal-directory, in-vm-acceptor, replication-colocated, http-connector, discovery-group, remote-acceptor, acceptor, connection-factory, remote-connector, in-vm-connector, legacy-connection-factory, grouping-handler, jms-topic, connector, security-setting, bridge, paging-directory, queue'
      
      ================================================================================
      
      09:21:26,938 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) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
      	at org.jboss.as.server.ServerService.boot(ServerService.java:355) [wildfly-server-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
      	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
      

            tcrawley Toby Crawley (Inactive)
            mnovak1@redhat.com Miroslav Novak
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: