[DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

clebertsuconic
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
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

christopher.l.shannon
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 <[hidden email]>
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
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

michael.andre.pearce
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" <[hidden email]> 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
>





Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

clebertsuconic
On Wed, Dec 11, 2019 at 12:15 PM <[hidden email]> wrote:
>
> 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.

There's probably a way. I don't know how to handle this though.
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

clebertsuconic
I figured this out.

The issue is that the attribute was already defined on the super type:

https://github.com/apache/activemq-artemis/pull/2916


it's probably the same issue you had before on queue type.

On Wed, Dec 11, 2019 at 12:41 PM Clebert Suconic
<[hidden email]> wrote:
>
> On Wed, Dec 11, 2019 at 12:15 PM <[hidden email]> wrote:
> >
> > 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.
>
> There's probably a way. I don't know how to handle this though.



--
Clebert Suconic
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

clebertsuconic
so, IBM's implementation seems to care about the double definition
while it silently fails on openJDK. I'm not sure which one is correct,
but removing the duplicate definition will ix the issue.

On Wed, Dec 11, 2019 at 1:51 PM Clebert Suconic
<[hidden email]> wrote:

>
> I figured this out.
>
> The issue is that the attribute was already defined on the super type:
>
> https://github.com/apache/activemq-artemis/pull/2916
>
>
> it's probably the same issue you had before on queue type.
>
> On Wed, Dec 11, 2019 at 12:41 PM Clebert Suconic
> <[hidden email]> wrote:
> >
> > On Wed, Dec 11, 2019 at 12:15 PM <[hidden email]> wrote:
> > >
> > > 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.
> >
> > There's probably a way. I don't know how to handle this though.
>
>
>
> --
> Clebert Suconic



--
Clebert Suconic
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Issue with Running testsuite for Artemis using IBM JDK

christopher.l.shannon
Awesome, I'm glad you were able to figure it out and it was just a small
change to the schema.

On Wed, Dec 11, 2019 at 1:55 PM Clebert Suconic <[hidden email]>
wrote:

> so, IBM's implementation seems to care about the double definition
> while it silently fails on openJDK. I'm not sure which one is correct,
> but removing the duplicate definition will ix the issue.
>
> On Wed, Dec 11, 2019 at 1:51 PM Clebert Suconic
> <[hidden email]> wrote:
> >
> > I figured this out.
> >
> > The issue is that the attribute was already defined on the super type:
> >
> > https://github.com/apache/activemq-artemis/pull/2916
> >
> >
> > it's probably the same issue you had before on queue type.
> >
> > On Wed, Dec 11, 2019 at 12:41 PM Clebert Suconic
> > <[hidden email]> wrote:
> > >
> > > On Wed, Dec 11, 2019 at 12:15 PM <[hidden email]>
> wrote:
> > > >
> > > > 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.
> > >
> > > There's probably a way. I don't know how to handle this though.
> >
> >
> >
> > --
> > Clebert Suconic
>
>
>
> --
> Clebert Suconic
>