Does anyone have any ideas on how we could generate a catalog.xml file[1] that we could ship in docs/schema along with all our xsds?  This would provide a mapping between our xml namespace URNs and the associated xsd file in that same dir.

For simplicity's sake this could be limited to the server / subsystem configuration schemas.

I think this would need to be handled by the WildFly galleon plugin. Such a catalog would need to combine data from the various maven modules that provide schemas. It's the WF galleon plugin feature pack generation or provisioning  functions that pull together data from all the various modules.

A not particular elegant possibility is to stick property files in the various 'schema' dirs in the source, e.g. https://github.com/wildfly/wildfly/tree/master/jaxrs/src/main/resources/schema. The properties map the urns to the xsd file names. Something in the galleon plugin knows to look for those and aggregates the contents and generates the catalog.

This question was sparked by a question from Fred Bricon on twitter: https://twitter.com/fbricon/status/1293911221771485185

[1] https://www.oasis-open.org/committees/entity/spec-2001-08-06.html

Best regards,

Brian