That's it! And it seems .. effective_symlink.setPermanent(false); effective_symlink.setDiscardPathInfo(false); effective_symlink.setDiscardQuery(false);
.. are unnecessary as they are defaults. I wasn't in this instance *needing* to see a fluent interface, but since you raise it <grin/> the addition of withXxxx(..) mthods where there are also setXxxx(..) methods would be a fantastic and easy start. They would return 'this' of course rather than void. - Paul On Thu, Nov 26, 2015 at 7:33 PM, Greg Wilkins <[email protected]> wrote: > > Paul, > > well a fluent style API would indeed be nice for this example. > > But Jetty is 20 years old and "fluent" was only applied to french/italian > back then :) So Jetty is pretty much a pile of beans in it's > fundamental style (although we are a little fluent in the latest client > API). It would be considerable bloat to go back over the entire API > and provide fluent alternatives to the bean style. > > Note also that you are being a little apple and orange in your comparison > between the styles as you have assumed in the bean style that none of the > defaults are right, but that they all are in the fluent example. > > So you really should just be comparing to: > > handlers.setHandlers(new Handler[] {new > MovedContextHandler(server,"/lib/angular","/lib/angular_v1.2.9") , > resource_handler, new DefaultHandler() }); > > > >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
