-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
11.0.0.Final
-
None
cache-container tag should not raise an XSD validation error when the jmx tag is before the transport tag
<cache-container xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:11.0 https://infinispan.org/schemas/infinispan-config-fragment-11.0.xsd" xmlns="urn:infinispan:config:11.0" name="default" statistics="true"> <jmx enabled="true" /> <transport cluster="${infinispan.cluster.name}" stack="${org.infinispan.test.server.cluster.stack:test-tcp}"/> </cache-container>
Error:
Invalid content was found starting with element '{"urn:infinispan:config:11.0":transport}'. One of '{"urn:infinispan:config:11.0":global-state, "urn:infinispan:config:11.0":local-cache, "urn:infinispan:config:11.0":local-cache-configuration, "urn:infinispan:config:11.0":replicated-cache, "urn:infinispan:config:11.0":replicated-cache-configuration, "urn:infinispan:config:11.0":invalidation-cache, "urn:infinispan:config:11.0":invalidation-cache-configuration, "urn:infinispan:config:11.0":distributed-cache, "urn:infinispan:config:11.0":distributed-cache-configuration, "urn:infinispan:config:11.0":scattered-cache, "urn:infinispan:config:11.0":scattered-cache-configuration, WC[##other:"urn:infinispan:config:11.0"]}' is expected.
It is not preventing the server from startup.
If we use in this order:
<cache-container xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:11.0 https://infinispan.org/schemas/infinispan-config-fragment-11.0.xsd" xmlns="urn:infinispan:config:11.0" name="default" statistics="true"> <transport cluster="${infinispan.cluster.name}" stack="${org.infinispan.test.server.cluster.stack:test-tcp}"/> <jmx enabled="true" /> </cache-container>
No XSD validation error.
