Re: [wtp-dev] Question about XML Catalog Contributions

[Jesper Steen Møller <jesper@xxxxxxxxxxxxx>]

We had this problem in XSL Tools, and ended up writing a specialized
resolver for it which peeked the version and returned the correct
schema. Having to write a resolver for each such schema doesn't scale
well in the general case, and is hidden from the user (i.e. doesn't
show up in the catalog), but it gets the job done.

I forget if the XML Catalog spec welcomes extensibility, but since
processors such as Xerces resolve schema locations by looking at 'uri'
entries in the catalog, it would make sense to add it there, using
e.g. xpath:

  <uri name="http://java.sun.com/xml/ns/persistence/orm";
      uri="file:///some/path/persistence-orm-1.0.xsd">
  <uri name="http://java.sun.com/xml/ns/persistence/orm";
      uri="file:///some/path/persistence-orm-2.0.xsd"
      catx:version="2.0"/>

using the catx:version attribute as a tie-breaker when matching
catalog entries (this assumed that the version is an attribute on the
root element). Or, even more general:

  <uri xmlns:orm="http://java.sun.com/xml/ns/persistence/orm";
      name="http://java.sun.com/xml/ns/persistence/orm";
      uri="file:///some/path/persistence-orm-2.0.xsd"
      catx:test="//orm:entity-mappings/@version = '2.0'"/>

I guess this could be prototyped into the Eclipse Catalog support to
see if it is viable.

However, the standards compliant way is to use XML Schema 1.1 which
supports conditional type assignment, so it will be possible to have a
schema for entity-mappings which has a dynamically determined type for
any given particle.  But this requires involvement of the schema
author, and commitment to XML Schema 1.1.


-Jesper
On Fri, Oct 2, 2009 at 10:45 PM, Paul Fullbright
<paul.fullbright@xxxxxxxxxx> wrote:
>
> Does anyone know if there is a way to take document version into consideration when registering a schema for a namespace?
>
> Java Persistence uses the same namespace for all versions of their documents, and so it seems only possible to register the latest version of the schema for validation for that namespace, and documents such as:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <entity-mappings version="1.0"
>   xmlns="http://java.sun.com/xml/ns/persistence/orm";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> </entity-mappings>
>
> show up as invalid since the version does not match the fixed value of "2.0" required by the latest version of the schema.  (Also, any new elements or attributes for 2.0 would show up as valid, even if not valid for 1.0.)
>
> --
> Paul Fullbright
> Eclipse Java Persistence Tools (Dali) Development
> Oracle
>
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev