Recent changes to the XMLSchema files

[Damiano Albani]

Hello,

I'm curious if there have been changes made today to the .xsd files provided on http://www.jgroups.org/schema/.

Because I see the following entries having a last modified date of today:

relay.xsd        2024-02-12 14:44  2.2K
jgroups.xsd      2024-02-12 14:44  412K
jgroups-5.3.xsd  2024-02-12 14:44  409K
jgroups-4.2.xsd  2024-02-12 14:44  412K

I'm asking because an XML validation process of mine that used to succeeded, suddenly started to fail today.

This validation is about checking if an Infinispan configuration files is correct according to the Infinispan XSD, which in turn references the JGroups XSD.

As in:

xmllint --noout --schema infinispan-config-14.0.xsd my-ispn-conf.xml

I then get following error:

http://www.jgroups.org/schema/relay.xsd:9: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element', attribute 'type': References from this schema to components in no namespace are not allowed, since not indicated by an import statement.

(repeated for lines 9, 15, 21 22, 29, 44 and 57)

Again, as I mentioned above, this validation broke unexpectedly today, so I guess this could have to do with the recent changes on http://www.jgroups.org/schema/, I assume.

Regards,

--

Damiano Albani

[Bela Ban]

Hi Damiano

I did update the web site this week, but I didn't modify relay.xsd (I
last modified it ~1 year ago).

I'm afraid I'm not an XML/schema expert, so perhaps ask on the
Infinispan ML?

> --
> You received this message because you are subscribed to the Google
> Groups "jgroups-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jgroups-dev...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jgroups-dev/64217f71-42bc-4319-a0fc-86efeb17f4d3n%40googlegroups.com
> <https://groups.google.com/d/msgid/jgroups-dev/64217f71-42bc-4319-a0fc-86efeb17f4d3n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Bela Ban | http://www.jgroups.org

[Damiano Albani]

Hi Bela,

I don't think the problem is related to Infinispan.

My intuition is that it just happened with an Infinispan configuration because it relies on an XML Schema from JGroups.

I'm curious as to what changes were made on 2024-02-12 to the files hosted at http://www.jgroups.org/schema/.

I don't have access to a cache so I can't personnally compare the before/after situations.

And what about the difference in the content of relay.xsd between https://github.com/belaban/JGroups/blob/master/conf/relay.xsd and http://www.jgroups.org/schema/relay.xsd?

Shouldn't they be identical?

Regards,

[Bela Ban]

You're right: http://www.jgroups.org/schema/relay.xsd is not what you'll
find in https://github.com/belaban/JGroups/blob/master/conf/relay.xsd. I
think I inadventently copied relay.xsd from either the 4.x or 3.6
branches (2.2k). The relay.xsd from master is 5.1k.
Investigating...

> <http://www.w3.org/2001/XMLSchema%7Delement>',

> https://groups.google.com/d/msgid/jgroups-dev/7285f790-0e59-4697-9891-5b060f2095e7n%40googlegroups.com
> <https://groups.google.com/d/msgid/jgroups-dev/7285f790-0e59-4697-9891-5b060f2095e7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Bela Ban]

The problem was that the ant build checked if a schema was already
present before copying it. Because the schema for 4.x was already
present, it skipped copying the schema for 5.x.
I changed this to overwrite the schema in precedence of 5 > 4 > 3.

I updated the websote; the schemas should now be up-to-date.
Cheers

[1] https://github.com/belaban/jgroups.org

On 13.02.2024 14:16, Damiano Albani wrote:

> <http://www.w3.org/2001/XMLSchema%7Delement>',

> https://groups.google.com/d/msgid/jgroups-dev/7285f790-0e59-4697-9891-5b060f2095e7n%40googlegroups.com
> <https://groups.google.com/d/msgid/jgroups-dev/7285f790-0e59-4697-9891-5b060f2095e7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Damiano Albani]

My test now passes, but I think I now get a warning that wasn't there before:

http://www.jgroups.org/schema/fork-stacks.xsd:9: element import: Schemas parser warning : Element '{http://www.w3.org/2001/XMLSchema}import': Skipping import of schema located at 'http://www.jgroups.org/schema/jgroups-4.0.xsd' for the namespace 'urn:org:jgroups', since this namespace was already imported with the schema located at 'http://www.jgroups.org/schema/jgroups-5.2.xsd'.

Probably due to http://www.jgroups.org/schema/fork-stacks.xsd referring to "jgroups-4.0.xsd".

Oh, and another unrelated thingie, I saw that the following lines appears twice in http://www.jgroups.org/schema/jgroups.xsd:

<xs:import namespace="urn:jgroups:relay:1.0" schemaLocation="relay.xsd"/>

[Bela Ban]

Correct, another oversight: I changed the ref to jgroups.xsd instead of
jgroups-4.0.xsd.
Thanks

> https://groups.google.com/d/msgid/jgroups-dev/621d73b5-d5b2-4fe6-884d-08d070ba7388n%40googlegroups.com
> <https://groups.google.com/d/msgid/jgroups-dev/621d73b5-d5b2-4fe6-884d-08d070ba7388n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Tristan Tarrant]

There is a long-standing problem with JGroups schemas that I would like to fix at some point:

the (versioned) jgroups-5.2.xsd imports the (unversioned) relay.xsd and fork-stacks.xsd. In turn, fork-stacks.xsd imports http://www.jgroups.org/schema/jgroups.xsd which then references other (potentially incompatible) relay.xsd and fork-stacks.xsd schemas.

I have created https://issues.redhat.com/browse/JGRP-2764 to track this.

Tristan

To view this discussion on the web visit https://groups.google.com/d/msgid/jgroups-dev/15c471b1-5836-45c8-b436-a328a8de7510%40mailbox.org.