AW: a scripted attribute definition example from the wiki

[Ortner Nikolaus]

> Anyway, there's now additional text about the warning (and the missing
> sourceAttributeID was added), so others shouldn't run into those
> issues in the future.

Well - you get a similar error when using nested attribute definitions and a sourceAttributeID used twice (e.g. when referencing a mapped attribute, attributeID unspecified, and you are not creative enough to generate another name for the unnamed): 

    <resolver:AttributeDefinition xsi:type="ad:Simple" id="personaluniquecode" sourceAttributeID="perskz">
        <resolver:Dependency ref="perskzMapping" />
        <resolver:AttributeEncoder 
...
    </resolver:AttributeDefinition>
    
<resolver:AttributeDefinition xsi:type="ad:Mapped" dependencyOnly="true" id="perskzMapping" sourceAttributeID="perskz">
       <resolver:Dependency ref="databaseresolver" />
       <ad:ValueMap>
            <ad:ReturnValue>urn:schac:personalUniqueCode:int:studentID:AT:$1</ad:ReturnValue>
            <ad:SourceValue>^([0-9]{10})$</ad:SourceValue>
       </ad:ValueMap>
    </resolver:AttributeDefinition>
    

WARN [net.shibboleth.idp.attribute.resolver.PluginDependencySupport:144] - Plugin 'personaluniquecode' was defined with a sourceAttributeID 'perskz', but the attribute definition 'perskzMapping', specified as a <Dependency> will be used as well.

Regards.