[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148962#comment-14148962
]
Karl Wright commented on CONNECTORS-345:
----------------------------------------
>From Abe Shinichiro:
1. I came to mind CONNECTORS-345.
2. Currently I have to create scripts in production:
startup.sh --
java -jar start.jar
echo $! > mcf.pid
shutdown.sh --
kill cat(mcf.pid) <-- MCF's embedded Jetty example can't call
agent-shutdown AFAIK but this script isn't cool.
3. start.jar command line options are useful.
http://www.eclipse.org/jetty/documentation/current/start-jar.html#d0e8418
4. If we can separate Jetty-lib and mcf-lib, we could deploy Tomcat. Of course
combined.war can do that though.
I thought additional jars could copy to another directory, and might load these
using Custom ClassLoader.
http://www.eclipse.org/jetty/documentation/current/jetty-classloading.html
5. But If users don't want to config jetty.xml(e.g. thread pool,
requestHeaderSize and so on in jetty.xml --
http://wiki.eclipse.org/Jetty/Howto/Configure_Connectors),
I will drop these suggestions.
> 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)
