I see your point about keeping parameter names the same across connectors as well as the ability to provide default values for them. I'll rethink this a bit.
Thanks, Kevin On Nov 28, 2007 10:15 AM, Jerome Louvel <[EMAIL PROTECTED]> wrote: > > Hi Kevin, > > I propose that the server properties for the Jetty connectors be > > dynamically set via refllection instead of hard coding the setter calls into > > the Http(s)ServerHelper. > > > > As it stands now, the helper classes are prone to an "arms race" with > > Jetty because Restlet need to be updated every time new parameters are added > > to the Jetty connectors. This problem was made clear by the lack of support > > for the various trust store properties. > > > That's true there is an integration delay involved, even though we try to > stay closely synchronized with Jetty releases. I'm not sure if there is a > need to be that dynamic here. > > This opens up the door for users to be able to specify their own > > connectors via a "connectorClass" property or something similar. All of the > > necessary properties are either Strings, booleans or ints so doing a > > conversion would not be a huge issue. > > > I do see your point of using reflexion and parameters for property > injection. The main issue I see with this approach is that we wouldn't be > able to use consistent parameter names across the various connectors or to > easily set our own default values. Also, the integration of external > connectors requires more than just setting property of a given class > instance. There will always be a need for manual glue code. > > If you feel strongly about this one, I suggest that you create a RFE. I'd > also like to get other opinions. > > Best regards, > Jerome > >
