Hi Teemu,
Sorry, I meant to reply to group instead of individually...Sending to the group so others can follow and participate.
I like the idea of having the option of just passing in an external configuration file. How about having an element or attribute on the the jetty section of systemConfig.xml that points to an external Jetty XML file that is placed in the server config directory? If this element is set, any Jetty configuration in systemConfig.xml is ignored. Could you file an issue in JIRA against 3.0 so we can track this?
Jim
---------- Forwarded message ----------
From:
Teemu Hiltunen <hiltune...@gmail.com>Date: Fri, Sep 11, 2015 at 6:56 AM
Subject: Re: Fabric3 Jetty configuration
To: Jim Marino <
jim.m...@gmail.com>
Hi Jim!
Your reply came only to me and not to the group - was that intentional?
Anyways, I can look into this and create a pull request when I have done it. At the moment I do not know what other configuration properties should be supported besides that request field size limit.
It is not the best solution, I think, that Jetty parameters have to be added like this - one by one when needed - but it would be a too big change to support configuring Jetty "natively" some how in Fabric3. Like something like this:
https://wiki.eclipse.org/Jetty/Tutorial/Embedding_Jetty#Configuring_a_File_Server_with_XML
--teemu