Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
This repository was archived by the owner on Nov 9, 2022. It is now read-only.

Excluded elements in fields sometimes won't bootsrap #220

@paxtonhare

Description

@paxtonhare

When defining a field with excluded elements in ml-config.xml you might be tempted to leave out unused options:

              <field-name>stuff</field-name>
              <include-root>true</include-root>
              <included-elements></included-elements>
              <excluded-elements>
                  <excluded-element>
                      <namespace-uri>http://www.namespace.com</namespace-uri>
                      <localname>things</localname>
                  </excluded-element>
              </excluded-elements>
          </field>

Left out of the above xml are:

                      <attribute-namespace-uri/>
                      <attribute-localname/>
                      <attribute-value/>

The roxy code to create an excluded element passes these to the function as () but the admin api really wants "".

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions