manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-345) Jetty Configuration Support
Date Tue, 30 Sep 2014 06:43:34 GMT


Karl Wright commented on CONNECTORS-345:

Hi Abe-san,

Assuming you can get CONNECTORS-1050 resolved, I think the trick of having a shutdown handler
in jetty makes sense for both the combined war process AND the "start" process.  Since there's
now a start-options.env for the "start" process, the example can include the shutdown token
for that too, as well as a shutdown script.

I don't think we should rely on "curl", however.  It's another dependency which we'd have
to list, and it's not really necessary.  It may be better to have a single class (in, say,
mcf-script-engine.jar) which can issue the shutdown post.  All the necessary java HTTP support
is there, so this should be straightforward to do.

> Jetty Configuration Support
> ---------------------------
>                 Key: CONNECTORS-345
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework core
>    Affects Versions: ManifoldCF 0.4
>         Environment: Jetty Configuration
>            Reporter: Michael J. Kelleher
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 2.0
>         Attachments: CONNECTORS-345-sample.patch
> Can the single process example be extended to support Jetty configuration?
> 1) jetty.xml
> 2) webdefault.xml
> 3) OPTIONS=.... along with their corresponding XML config files, most importantly the
JMX option, Server,ajp,setuid would be nice to have

This message was sent by Atlassian JIRA

View raw message