On 27/11/13 17:34, Stuart Douglas wrote:
>
> One feature within JBoss Web was that at deployment time if an
> authentication mechansism is already set on a web app the default
> mechanism handling was skipped - we may also want to consider this to
> allow deployers within WildFly to take over this handling.
Not sure exactly what you mean here, an extension can remove other mechanisms if it
desires.
What I mean here is making sure we don't have mechanisms being added
from multiple locations - but maybe if the deployers are just setting
names and factories and Undertow calls the factories that double
processing of methods would not occur.