Scripted Attribute resolution and legacy support.

[Cantor, Scott]

On 3/26/13 8:12 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>One open question is that the current API allows modification of
>attributes
>which were dependencies of, but not the output of, the resolver.  Whilst
>we
>cannot stop this continuing to work (via the getNativeAttribute method), I
>do not think that we need to provide legacy support for it except for the
>slightly odd case from the wiki where the input attribute is also the
>output
>attribute - indeed it is the existence of this script in the wiki which
>finally forced me into adding the encapsulating class.

I don't think that's the case. I think the example is the case where the a
data connector includes an attribute that happens to have the same short
name as the attribute produced by the script.

-- Scott