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

VDX - pretty print should inform user that JBOSS_HOME/docs/schema is not available

XMLWordPrintable

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

      VDX - pretty print should inform user that JBOSS_HOME/docs/schema is not available, probably on DEBUG level.

      • open standalone.xml
      • locate webservices subsystem
      • add <mmodify-wsdl-address>true</mmodify-wsdl-address> under <wsdl-host>...</wsdl-host>
      • remove jboss-eap-7.1/docs
      • run standalone.sh

      VDX falls back to original behavior, no message about missing docs directory in server log
      For the record you need to change jboss-eap-7.1/standalone/configuration/logging.properties directly as changes from standalone.xml are not propagated when boot fails.

      I would expect message about missing docs/schema directory on DEBUG level. I think INFO is too much, but probably possible considering https://developer.jboss.org/docs/DOC-55722

      VDX or its integration cannot output any WARN level or above error message related to its 
      failure to process unless the original exception that would have been logged has already 
      been logged. In practice this likely means VDX problems must be logged at INFO or below. 
      The point here is the meaningful-to-the-user problem is the original one not the VDX one, 
      so it must come first.
      

      cc tcrawley

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

                Created:
                Updated:
                Resolved: