Alpha2 Metadata Error on Start

[Marvin Addison]

> my guess is this
> has to do with the attribute mapper reading from metadata as part of
> the encoders.

Looks like it's happening on a metadata refresh of the example MD file:

16:08:03.440 - DEBUG
[org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver:302]
- Error occurred while attempting to refresh metadata from
'/apps/local/idp/metadata/example-metadata.xml'
net.shibboleth.utilities.java.support.logic.ConstraintViolationException:
Component ID can not be null or empty
...
[rest of stack trace]
16:08:03.443 - INFO
[org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver:314]
- Next refresh cycle for metadata provider
'/apps/local/idp/metadata/example-metadata.xml' will occur on
'2014-07-31T20:13:03.440Z' ('2014-07-31T16:13:03.440-04:00' local
time)
16:08:03.460 - ERROR
[org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:193]
- Metadata provider failed to properly initialize, fail-fast=true,
halting
net.shibboleth.utilities.java.support.component.ComponentInitializationException:
Error refreshing metadata during init
...
[stack trace as posted previously]

Could still be an attribute-metadata interaction as you said, but it's
pretty clearly happening on metadata refresh; maybe the refresh is
triggered by something in the attribute definitions.

M