I looked at code committed and I have another idea to add, in case we are going to use the Jett implementation we can detect whether there is a jetty.xml - jetty configuration - file under our config directory - or we can define the path by a property - to configure the jetty server, in case we didn't find the jetty.xml we can have a default configuration object to use, or even better we can set a default configuration file and users can edit it on demand. I will study the code and start to do it.
On Jan 6, 2008 4:00 AM, Mohammad Nour El-Din <[EMAIL PROTECTED]> wrote: > Well Dain read my mind regarding the configuration property but the new > thing is detecting the Jetty classes. I can play with the new code and see > how it runs. > > > On Jan 5, 2008 12:50 PM, David Blevins <[EMAIL PROTECTED]> wrote: > > > > > On Jan 3, 2008, at 12:29 PM, Dain Sundstrom wrote: > > > > > I added code to switch from the OpenEJB http server to Jetty when > > > the Jetty classes are available. You can also explicitly state > > > which http server impl will be chosen by setting the 'impl' property > > > in the HttpEjbServer properties. > > > > > > Let me know if you have any problems. Also, David if you have time > > > can you review my changes? I'm not sure it is how you wanted this > > > to work (I just hacked something quickly). > > > > Cool. Mohammad had mentioned he was going to work on this[1]. > > Mohammad how does this compare to what you were thinking of doing? > > > > -David > > > > [1] > > http://www.nabble.com/Re%3A-Webservice-support-in-standalone-OpenEJB-p14478246.html > > > > > > > -- > Thanks > - Mohammad Nour -- Thanks - Mohammad Nour
