ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (Commented) (JIRA)" <>
Subject [jira] [Commented] (ACE-259) Support for metatype schema v1.1 (and beyond)
Date Fri, 13 Apr 2012 15:44:18 GMT


Bram de Kruijff commented on ACE-259:

Comitted improved/efficient checking in r1325804

Note on backward compatibility..

The new implementation, like the old implementation, does no XML validation. However, the
old implementation allowed basically anything as long as the first document node (whatever
it is) has an attribute with qName "xmlns:metatype" and a value that matches a known namespace.
The new implementation says: The first element must have (implied) localName "MetaData" and
a namespace (either default or prefixed) that matches a known namespace.

Thus, really awkward files that may have been accepted by the old implementation may be rejected
by the new one.  By example:

These examples will now be rejected:
<MetaData xmlns:metadata="">

These examples will now be accepted:
<MetaData xmlns="">

<foo:MetaData xmlns:foo="">

<metatype:MetaData xmlns:metatype="">

> Support for metatype schema v1.1 (and beyond)
> ---------------------------------------------
>                 Key: ACE-259
>                 URL:
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Bram de Kruijff
>            Assignee: Bram de Kruijff
> The configuration helper implementation hardcodes a check for "",
but v1.1 and v.1.2 are also valid schemas. AFAICS there is no regression risk in accepting
v1.1 and 1.2 as long as the provider autoconf rp can handle them. Unfortunatly, there is no
way to express version constraints on this level.
> So..
> 1) Create seperate helpers for v1.1. & v1.2
> 2) Make this helper accept v1.1 & v.1.2
> 3) Rely on org.apache.felix.metatype.MetaDataReader to determine validity
> IMHO option 1 is unnecessarily heavy, option 2 is the easiest fix and option 3 the most
elegant and robust solution. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message