[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152862#comment-14152862
]
Karl Wright edited comment on CONNECTORS-345 at 9/30/14 6:45 AM:
-----------------------------------------------------------------
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 (in
ManifoldCFCombinedJettyRunner) AND the "start" process (in
ManifoldCFJettyRunner). 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.
What do you think?
was (Author: [email protected]):
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: https://issues.apache.org/jira/browse/CONNECTORS-345
> 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
(v6.3.4#6332)
