External authentication: MVC controller as alternative to servlet

[Brent Putman]

Just getting to some old threads...


On 9/17/15 12:21 PM, Cantor, Scott wrote:
>
> I think the beans are declared in part because of the SWF docs. To enable SWF you have to override the default handler mapping beans, and I think Chad just added in the beans that are declared normally by Spring that would be removed by the explicit mapping bean (thus the comment "Have to enumerate them all explicitly b/c we're overriding the built-in defaults.").

I think that was actually me, from the original testbed.  And your
interpretation is correct: Spring MVC declares certain impls as
defaults if not otherwise wired.  See spring-webmvc jar, resource
org.springframework.web.servlet.DispatcherServlet.properties, where it
declares these defaults:


org.springframework.web.servlet.HandlerMapping=org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping,\
   
org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping

org.springframework.web.servlet.HandlerAdapter=org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter,\
    org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter,\
   
org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter



So my reason for declaring them all in the original testbed wiring was
nothing other than "add the SWF ones, but keep the other defaults the
same".  And of course the testbed SP is using annotations, so that one
actually needed to be there anyway.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150923/2ac2aec1/attachment-0001.html>