Hi Gerhard, thanks for your response. Right now we use crossvalidators, also custom implementations, and some AbstractStartupListener implementations. Until now I only recognized the problem with bv.
I can workaround it with my own implementation of application, registering the factory in the faces-config.xml in WEB-INF. I filed a jira-ticket, see [1]. Maybe it's enough to add a configuration Option in ExtValApplicationFactory, to deactivate the wrapper, as already stated there. markus [1] https://issues.apache.org/jira/browse/EXTVAL-162 -- View this message in context: http://myfaces.10567.n7.nabble.com/EXTVAL-DefaultValidatorId-will-not-be-set-tp122266p122271.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
