[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148966#comment-14148966
]
Karl Wright commented on CONNECTORS-345:
----------------------------------------
Hi Abe-san,
For the single-process example, since there is no external communication with
the process, the only way to shut it down is to kill it, as you have
implemented above. I don't see how your suggestion would change that in any
way?
As for your comment that people may not want to configure jetty, I think we can
assume that they do. You also, though, seem to imply that people might want to
use Tomcat for the single-process example. That seems to me to be unlikely,
since (as you point out) we have a combined war for exactly that purpose. The
reason we ship jetty at all is because (a) it makes a very easy example, and
(b) we use it in tests.
> 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
>
>
> 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)
