[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154275#comment-14154275
]
Shinichiro Abe commented on CONNECTORS-345:
-------------------------------------------
bq.So I wonder if there is a jetty method we can call that will configure our
jetty instance using an xml configuration file.
The example is
[here|https://github.com/eclipse/jetty.project/blob/master/examples/embedded/src/main/java/org/eclipse/jetty/embedded/ExampleServerXml.java].
In fact, Jetty itself uses
[XmlConfiguration|http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/xml/XmlConfiguration.html].main(args)
when starting by start.jar. See Also:
[org.eclipse.jetty.start.Main|https://github.com/eclipse/jetty.project/blob/master/jetty-start/src/main/java/org/eclipse/jetty/start/Main.java#L279]
The args are Resource Objects[] which can have jetty.xml, jetty-deploy.xml, and
*.properties etc.
If MCF will use XmlConfiguration class, we will have to write mcf-jetty.xml in
which we define all configuration.
bq.It may be better to have a single class (in, say, mcf-script-engine.jar)
which can issue the shutdown post.
+1. This is cool.
[Here|https://github.com/eclipse/jetty.project/blob/master/jetty-server/src/test/java/org/eclipse/jetty/server/handler/ShutdownHandlerTest.java]
and
[here|https://github.com/eclipse/jetty.project/blob/master/jetty-server/src/main/java/org/eclipse/jetty/server/handler/ShutdownHandler.java#L57]
are useful to impl that.
Thanks.
> 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)
