Community
Participate
Working Groups
Build Identifier: As according the http://www.osgi.org/xmlns/metatype/v1.1.0 schema an empty <MetaData/> should be supported (the OCD, Designate, xsd:any element have all minOccurs="0"). However, the implementation will report the following error when parsing an empty <MetaData/> element: [ERROR ] DataParser.finished() Missing element Designate (Reference ID = <missing argument>. Bundle:org.eclipse.equinox.metatype(id=12) Reproducible: Always
Targeting this for 3.8. It's true that an empty <MetaData/> element is technically correct albeit completely useless. What do you think the desired behavior would be when encountering one? Process it silently or issue a message at some level in order to protect users from themselves?
I would issue at least a warning. What is the reason to have an empty <MetaData/> element? I agree with John, this seems like it would be useless to do.
It might be useless but it's not an error. So getting a warning message instead of an error would be great.
Move all 3.8 bugs to Juno.
Note the conversation occuring in bug 350201 is applicable here too. If a bundle only contains metadata files with an empty <MetaData/> element, it will act as if it had no metadata and be converted into a tracker.
Created attachment 198941 [details] proposed patch This patch simple changes the log level from error to warning. Note this patch also includes bug 350201.
Patch released.