Jetty deployment

Tom Zeller tzeller at dragonacea.biz
Wed Sep 17 13:41:51 EDT 2014


On Wed, Sep 17, 2014 at 12:36 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/17/14, 1:31 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>>
>>As Scott sort-of said, we'd also need to provide our own HTTPS and SSL
>>modules as well, since Jetty's defaults are not altogether suitable
>>for our needs.
>
> I didn't think of it, but yes, having our own modules defined would
> probably be the way to go for a bundled Jetty. The problem with using that
> trick on the regular version is that you have to go mucking with the
> distribution folders to add modules, and the whole point of jetty-base is
> not to have to touch the distribution.

I thought that modules followed the jetty-base-then-jetty-home
configuration resolution rules, but I'd have to try it. When I was
fooling around with Jetty, the idea was that our modules could be
defaulted in our bundled distribution of jetty-base, but added to a
regular distribution by copying, or shudder, via automatic download -
I'd guess we'd have to provide a patch to check signatures ;-)


More information about the dev mailing list