Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
I created a contribution-point whose contributions are based on a schema that is so simple (one element with one attribute of type string) that I decided to not specify any conversion or rules elements within the schema. My thought was that the schema would provide syntax checking while my service's property would be set to a list of org.w3c.dom.Element objects. While no errors were flagged, my setter was always called with an empty list. When I updated by contribution-point to no longer reference the schema, my setter was called with the expected list of one Element object.
If it is legal for the schema's top-level elements to not have conversion/rules sub-elements, then the dom object representing each of those elements should be included in the list of contributions injected into the service. If it isn't legal, the XML parser should flag an error.