JSP files in the war

[Cantor, Scott]

On 5/18/14, 4:50 AM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>On 5/17/14 8:35 PM, Tom Zeller wrote:
>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].

It doesn't have to be if you're explicitly defining the flow ID, which I
am, mostly.

>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.

Yes, exactly. If it weren't for that, I probably would have mounted the
flows under a common prefix to preserve the root for static content, but
the best option I can see is just to reverse that and reserve /resources
(or whatever) for web content, and the rest for flows.

I'm sure it's obvious, but *view* JSPs are best confined to some place
under WEB-INF so they can't be invoked directly, whereas JSPs meant to be
run by the client would then be under /resources.

As an aside, it would be nice eventually if the installer could prompt at
install time for JSP vs. Velocity views. If JSP is selected, we could just
not install the Velocity views.

Rod mentioned this on the call, I think it would be nice to have a
conf.defaults created, with the "stock" install tree, and then create
conf/ with the files based on the options chosen, or whether it's an
upgrade or not. Then all the starting files are right there in the system
to compare with or copy over.

-- Scott