Alpha2 Metadata Error on Start

Cantor, Scott cantor.2 at osu.edu
Fri Aug 1 10:52:38 EDT 2014


On 7/31/14, 5:13 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>Not sure if this has been said or not, but looks to me like the root
>cause is that the filesystem metadata provider (wherever/whichever config
>it's reading) doesn't have an 'id' attribute defined.  Looks like the
>AbstractMetadataProviderParser just unconditionally does this:
>
>builder.addPropertyValue("id", element.getAttributeNS(null, "id"));

I think that's because the schema requires an id attribute be set, so it's
assuming it's there. And it is there in the sample config.

>I don't know if it should be doing that or not based on what we decided
>about id attributes, etc; I think Chad added a lot of UUID default ids in
>ctors like that way back.  Or maybe I did this one based on his existing
>model.

I think we've mostly decided to stop doing that.

>But I think that actual fix is to just figure out what config is actually
>loading here and check that the filesystem provider has an id attribute.
>If it does have one, then there must be something else fishy going on
>somewhere with the parsers or something...

Exactly, there is something really odd happening here.

-- Scott



More information about the dev mailing list