Jetty deployment

[Cantor, Scott]

On 9/16/14, 9:56 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>I'm currently read the potted configuration that we ship with the Alpha
>and
>using that to swap in some basic Jetty config skills.
>
>Before I develop too many ideas, this mail is a trawl to those with Jetty
>expertise (committers and non-committers alike) as to what their
>expectations are.

We've talked about the setuid issue ad nauseum, but I guess in Windows
terms that's more tractable.

I can only speak for myself, but in my experience, the whole ini file
thing is basically a waste of time. The idea there was that you'd set
properties and not have to copy or edit the XML config files for
particular modules, which makes upgrades much easier. In practice, that
doesn't work because the properties you can set are too limiting. To add
more property replacements, you have to edit the XML files, and having
done that, you just lost the only real benefit of having the properties.

It could be that the requirements here are less advanced than mine, but I
think you'll find that to create appropriate defaults, you'll probably
need more properties than you can set. Perhaps if we come up with a more
useful set, we can feed that back and get them to put the property
expressions into the distribution so they can be set without editing the
XML in the future.

One thing I do in mine is use the root webapp context as an open container
for various bits of stuff I need to make available on my IdP server. For
example, I use it to host my signed IdP metadata and key, my
documentation, various support pages, and a cgi-bin directory where I host
various shell scripts that handle issues with vendor SPs like
framebusting, or cases where I need to do IdP-initiated SSO.

-- Scott