Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-7858

The batch subsystem configuration doesn't validate in standalone-elytron.xml profile

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • None
    • Batch, Security
    • None
    • Hide

      Extend the StandardConfigsXMLValidationUnitTestCase in testsuite/integration/smoke to parse also the standalone-elytron.xml and run it.

      Show
      Extend the StandardConfigsXMLValidationUnitTestCase in testsuite/integration/smoke to parse also the standalone-elytron.xml and run it.

    Description

      The security-domain element in batch-jberet subsystem is not placed correctly in standalone-elytron.xml profile.

      The current configuration in the profile is:

      <subsystem xmlns="urn:jboss:domain:batch-jberet:2.0">
          <default-job-repository name="in-memory"/>
          <security-domain name="ApplicationDomain"/>
          <default-thread-pool name="batch"/>
          <job-repository name="in-memory">
              <in-memory/>
          </job-repository>
          <thread-pool name="batch">
              <max-threads count="10"/>
              <keepalive-time time="30" unit="seconds"/>
          </thread-pool>
      </subsystem>
      

      And XSD (wildfly-batch-jberet_2_0.xsd) says:

      <xs:sequence>
          <xs:element name="default-job-repository" type="namedType" minOccurs="1" maxOccurs="1">
          </xs:element>
          <xs:element name="default-thread-pool" type="namedType" minOccurs="1" maxOccurs="1">
          </xs:element>
          <xs:element name="restart-jobs-on-resume" type="booleanType" minOccurs="0" maxOccurs="1">
          </xs:element>
          <xs:element name="security-domain" type="namedType" minOccurs="0" maxOccurs="1">
          </xs:element>
          <xs:element name="job-repository" type="job-repositoryType" minOccurs="1" maxOccurs="unbounded"/>
          <xs:element name="thread-pool" type="thread-poolType" minOccurs="1" maxOccurs="unbounded"/>
          <xs:element name="thread-factory" type="threads:thread-factory" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
      

      As a result the profile XML validation ends with error:

      cvc-complex-type.2.4.a: Invalid content was found starting with element 'security-domain'. One of '{"urn:jboss:domain:batch-jberet:2.0":default-thread-pool}' is expected.
      

      Attachments

        Issue Links

          Activity

            People

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: