[JIRA] Updated: (MDA-49) add stage to remove empty container elements

Ian Young (JIRA) noreply at shibboleth.net
Thu Mar 22 10:21:16 GMT 2012


     [ https://issues.shibboleth.net/jira/browse/MDA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Young updated MDA-49:
-------------------------

    Summary: add stage to remove empty container elements  (was: add stage to remove empty Extensions element)

I think this should be generalised to allow it to remove empty instances of a named container element (defined as one whose only significant content is a collection of elements).  The original need to strip empty Extensions elements becomes a configuration choice, but this means that the stage can be used for any of the many other containers (e.g., EntityAttributes).

> add stage to remove empty container elements
> --------------------------------------------
>
>                 Key: MDA-49
>                 URL: https://issues.shibboleth.net/jira/browse/MDA-49
>             Project: Metadata Aggregator
>          Issue Type: New Feature
>          Components: SAML Metadata
>    Affects Versions: 0.6
>            Reporter: Ian Young
>            Assignee: Ian Young
>             Fix For: 0.7
>
>
> The general Extensions element in SAML metadata has a requirement that it contain at least one child element.  This leaves any code which modifies an Extensions element by removing a child element with the possibility that a schema-invalid document may result.
> One approach to this is to impose the burden of ensuring schema validity on every stage which performs any manipulation on SAML metadata, which might work in some cases but can be quite onerous.
> Another approach is to provide a general stage which can fix up any Extensions elements which have become schema-invalid through whatever means.  This needs to be called only once, at the end of a series of potentially disturbing actions.
> Assigning this to myself; I plan to prototype an implementation in the UKf context.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the commits mailing list