[utilities COMMIT] /java-support/trunk/src/main/java/net/shibboleth/utilities/java/support/httpclient/HttpClientBuild...

[Cantor, Scott]

On 12/16/14, 9:26 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:


>
>I was looking at adding new names for the HTTP metadata providers schema
>and how to implement.  I guess you take the value of the new name, or if
>not there, then the old name.  Easy enough.

Yeah, no co-constraints to prevent both from appearing unless they're 
elements.

>I saw/remembered that we have some formerly deprecated attributes there,
>such as cacheDuration and maintainExpiredMetadata.  I assume in v2 we
>had those co-exist for awhile with the thing that replaced them, like
>we'd do there for the "Ssl" -> "TLS" ones.  Now in v3 we actually throw
>exceptions when those are encountered.  Since I imagine that the statue
>of limitations has run out... should those just be moved from the schema
>entirely?  People would then get some sort of schema validation error
>from Spring; currently they get a BeanDefinitionParsingException from us
>directly.  Is there really much difference?  Not saying we have to do it
>right now, but just looking to simplify.

I think we tentatively planned to go ahead for a release with them still 
present, and just produce the better error message, but probably pull them 
in a 3.1.

-- Scott