JSP files in the war

[Brent Putman]

On 5/17/14 8:35 PM, Tom Zeller wrote:
>> I just checked and see that we are mounting the
>> DispatcherServlet as the / path.  That probably does muck with
>> resolution of static resources.  So you probably do need the
>> <mvn:resources />.
> Checking my own understanding, given a URL of the form
>
>  http://host/contextPath/servletPath/pathInfo
>
> assuming the contextPath is /idp and given that we define profile flow
> IDs as profile/, the servletPath must be / because of how SWF by
> default constructs flow IDs based on pathInfo [1].


I'm not quite sure what you are asking, but I thought that in general in
SWF flows are just resolved relative to the dispatcher servlet path.  I
think that's what I did in my original testbed.  So the dispatcher
servlet doesn't *have* to be /.  It certainly doesn't in regular Spring MVC.

I infer that Scott just did it that way so that we can have flows like
"/profile/SAML/whatever" be consistent with the old v2 paths, but still
have other non profile flows under /.  I see "/c14n/" and "/authn/" ones
for example.  I hadn't really looked at all that until just now.  Looks
fine to me, if that was in fact the reason and the goal.  Just means
Spring MVC has to be involved for everything under /.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20140517/126046a0/attachment-0001.html