[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151637#comment-14151637
]
Karl Wright commented on CONNECTORS-345:
----------------------------------------
bq. FYI, if users want to configure Jetty, we can improve o.a.m.jettyrunner
using link:LikeJettyXml.html, although currently any requirements don't exist.
Hi Abe-san,
I think what this ticket was about was having a jetty.xml configuration file
somewhere that people could modify. In other words, they want ManifoldCF to
use jetty just like jetty was tomcat -- that is, you start jetty, and then
deploy the wars. But I think that the whole point of using Jetty in our case
is to make it simple for the user to use ManifoldCF. So I wonder if there is a
jetty method we can call that will configure our jetty instance using an xml
configuration file.
> 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)
