ESAPISecurityConfig hides current validators

[gprestia]

Hello,
when upgrading our version of java opensaml from 2.4.1 to 2.5.1 we noticed
an apparent regression in the behaviour of validators in our products.
 
By inspecting method DefaultBootstrap.bootstrap() we noticed that a new line
has been added: initializeESAPI()
This method replaces the current "security configuration impl class" of
ESAPI with "org.opensaml.ESAPISecurityConfig", thus changing the behaviour
at runtime.
By inspecting that class, we noticed an extremely minimalist implementation,
with most methods featuring empty implementations.

We are missing the rationale for such change and we are probably
misunderstanding the implementation of ESAPISecurityConfig. 
--> Could someone please clarify?

Rgds
Gregorio



--
View this message in context: http://shibboleth.1660669.n2.nabble.com/ESAPISecurityConfig-hides-current-validators-tp7584799.html
Sent from the Shibboleth - Developers mailing list archive at Nabble.com.