ECMA to access SubjectCanonicalizationContext in Resolver

Cantor, Scott cantor.2 at osu.edu
Tue Nov 10 16:03:02 EST 2015


>But that does raise the question of what happens the "2nd time thru", during the standard resolution time. Will the value set at c14n-time still be around, so a check to be sure it already has a value is sufficient to keep it from trying to access that context again? Or just test the context, and if null, assume this is already pat the c14n time?

Nothing is still around except for cached connector results. Attribute definitions are never cached. I don't recall if the result set caching is implemented in a way that would allow the scripted connector to have cached results, but I don't think so.

Either way, you would need the error handling there and just have it not resolve any data. I think it's generally cleaner to have a very separate attribute/connector sequence for that use case than anything running the rest of the time.

-- Scott



More information about the dev mailing list