If we were to change, I'd rather use a blueprint config coupled with some ConfigAdmin support so that we can change the jetty configuration more easily. Though I don't think it's that easy to switch, as pax-web needs to be enhanced I'd think.
On Thu, Dec 23, 2010 at 18:48, Charles Moulliard <[email protected]> wrote: > Hi, > > I would like to suggest that we use spring bean syntax to configure > the jetty server. As the spring beans xml syntax is much more > supported by all the developers, that would simplify the configuration > of the jetty.xml file instead of the proprietary syntax used. > > http://wiki.eclipse.org/Jetty/Howto/Spring > > Regards, > > Charles Moulliard > > Sr. Principal Solution Architect - FuseSource > Apache Committer > > Blog : http://cmoulliard.blogspot.com > Twitter : http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard > Skype: cmoulliard > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
