[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177467#comment-13177467 ]
Michael J. Kelleher commented on CONNECTORS-345: ------------------------------------------------ I can mess around with this tomorrow and see what happens and report back with my findings, if that is ok with you. I primarily need jmx and jetty.xml and webdefault.xml support for enabling application container BASIC authentication and server monitoring. The instance would be used in a production system and needs to be monitored and also prevent "the curious" from breaking stuff. I know tomcat could be used, but this is more self contained and portable. Also, I suspect, requires little or no administration, other than the initial jmx and auth support, which would become part of an "image" created for "deployment". Sent from my iPhone On Dec 29, 2011, at 7:11 PM, "Karl Wright (Commented) (JIRA)" > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira