Alpha2 Metadata Error on Start

[Cantor, Scott]

On 8/3/14, 9:43 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>Bug#1:  The mapper creation code has an assumption that getFriendlyName()
>returns non-null.  This needs to be fixed .  I have entered case IDP-458
>for
>that case.

Note that on the call we alluded to the fact that we probably should
eliminate all the implicit calls to setId, because these keep biting us. I
would suggest we do that here as well. If we can't get an ID set that
makes sense, then we should stop requiring IDs. I think that's been
basically an unhelpful concept for us.

>In the longer term there is a question of whether we should promote
>attribute mapping up to being a service offered by the attribute resolver.
>This would at mean that attribute mapper configuration errors would happen
>as a result of initialization of the attribute mapper.  Alternatively we
>could do is create the mapper when the encoder is initialized which would
>have much the same effect.   I'm not convinced - if the logging had been
>correct this would have been an easier problem to diagnose.

Yeah, I'm not sure we need to change everything just to compensate for a
bad log message. I think the lesson is, never call setId in code.

-- Scott