Adding new Attribute Interfaces to java-api.

[Cantor, Scott]

On 9/24/13 3:07 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>I am having a hard time with this thread and the rename-Attribute
>thread, I suggest that we talk on a dev call.

That's fine.

There aren't that many things I feel extremely strongly about when it
comes to Java, but avoiding classes where interfaces are usable is
definitely one of them. I cannot stand the lack of multiple inheritance in
the language, so I prefer to avoid going concrete until the last possible
moment.

>I would need to take more time to look through the v2 and v3 IdP and
>OpenSAML to see where Chad moved away from the
>Interface+Abstract+Concrete model to just Concrete. If we decide that
>we want to re-reverse that, then I think it will affect more than just
>the 4 classes mentioned in the OP, and we would need to define some
>sort of convention for which objects get an interface, because we
>think those are plug-in points.

I agree that it's not likely to be universal. Context for example is one I
keep trying to find, and then remember that the top level is BaseContext.
And no, I don't like that, but it doesn't bother me very much because
those aren't really pluggable in the same sense.

-- Scott