|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
The "filter" attribute we use on the "MetaData" tag, used to filter against available ConfigAdmin service registrations by the autoconf processor, is not allowed in the 1.0 schema [0]. Actually, you can't just slap it onto there in 1.1 schema [1] either due to the fact that is has (the default) "strict" processingContents directive. This unlike the "any" tags which have "lax" making live much easier.
Bottomline... formally there is no way to use the filter way and end up with a valid xml document. Informally, I have seen no code anywhere in ace, felix, amdatu that actually validates xml.
[0] http://www.osgi.org/xmlns/metatype/v1.0.0/metatype.xsd
[1] http://www.osgi.org/xmlns/metatype/v1.0.0/metatype.xsd