[
https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177465#comment-13177465
]
Karl Wright commented on CONNECTORS-345:
----------------------------------------
bq. It looks like some things have changed going from Jetty 6.1.26 and the
newest version 7.x. So, the dependencies for this will change a bit.
This is kind of what I was afraid of.
If it's relatively easy to port to using Jetty 7 I'd certainly be willing to do
it in the release 0.5 timeframe. If there are broad architectural changes,
and/or your requirements are going to require ManifoldCF to continuously
upgrade Jetty versions, then it's more of a tradeoff.
It should be pretty easy to see if Jetty 7 works right now with MCF, and that
would be the proper first step. Just delete the old jetty*.jar files from the
lib directory, drop down the new jetty jar files, and try running "ant test".
If that fails we'd need to figure out why. (The single-process example will
almost certainly fail because start.jar won't have the right manifest, but that
is easy to address.)
> 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
