That sucks some what on ibms behalf. I think we hit same issue a while back on some queue configs also.
Is there a way to possibly add an extra jar or something or manage the XML parse libs so theyre not dependent on jvm impl version. Get Outlook for Android On Wed, Dec 11, 2019 at 4:14 PM +0000, "Christopher Shannon" <[email protected]> wrote: Yeah I mean we can change the schema if we need. I did inheritance so I didn't have to copy and paste but as long as the result is the same I don't care how we change the schema. You could test it out locally and see if it works with copy/paste vs inheritance as I don't have an IBM JDK setup to test with. On Wed, Dec 11, 2019 at 11:03 AM Clebert Suconic wrote: > When you use an IBM JDK, the downstream property added to the XSD does not > work. > > I had dealt with this in the past, apparently the schema parser on the > IBM JDK does not know how to handle inheritance. > > > @Christopher Shannon is there a way we can just copy & paste > inheritance here, so we can pass this? I have always tested IBM JDK in > the past, and it stopped running after this change. > > > To replicate the issue, just run the broker using the IBM JDK, and you > should see this: > > > org.xml.sax.SAXParseException: ct-props-correct.4: Error for type > 'downstreamType'. Duplicate attribute uses with the same name and > target namespace are specified. Name of duplicate attribute use is > 'base'. > at > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown > Source) > at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) > at > org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown > Source) > at > org.apache.xerces.impl.xs.traversers.XSDAbstractTraverser.reportSchemaError(Unknown > Source) > at > org.apache.xerces.impl.xs.traversers.XSDComplexTypeTraverser.handleComplexTypeError(Unknown > Source) > > > > -- > Clebert Suconic >
