[
https://issues.apache.org/jira/browse/FELIX-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286241#comment-14286241
]
Carsten Ziegeler commented on FELIX-4687:
-----------------------------------------
There ar also two clarifications, not sure if we already implement
them:Metatype Service Specification Version 1.3 References
• Clarified that Meta Type Service will only search for ManagedService and
ManagedServiceFactory
service objects that implement MetaTypeProvider if no meta type resources are
found in the
bundle.
• Clarify that if multiple sources define the same Object Class Definition,
that Meta Type Provider
services must take precedence over Managed Service [Factory] objects
implementing MetaType-
Provider or Meta Type Resources.
Other than that there is nothing to be expected afaik
> Support v. 1.3 metatype namespace
> ---------------------------------
>
> Key: FELIX-4687
> URL: https://issues.apache.org/jira/browse/FELIX-4687
> Project: Felix
> Issue Type: New Feature
> Components: Metatype Service
> Affects Versions: metatype-1.0.10
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: metatype-1.0.12
>
>
> Support the R6 v 1.3 metatype schema version. The changes currently are:
> - new namespace
> - AD are now optional (not currently validated on earlier versions)
> - AD type "Char" spelling corrected to "Character".
> In line with the Eclipse metatype service I'm going to allow both "Character"
> and 'Char" in any namespace. If anyone objects I'm happy to change this to
> validate which namespace each is valid under.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
