Chris, [...] > Another thing I noticed is that using a base filename > in the DirectoryHandler no longer works. My older code had: > > DirectoryHandler staticFiles = > new DirectoryHandler( this, webUri, "index" ); > > which didn't pull up the 'index.html' page on a directory request. > Changing it to: > > DirectoryHandler staticFiles = > new DirectoryHandler( this, webUri, "index.html" ); > > worked fine. Do you think it's a good idea to have a set of possible > files, similar to the Apache directive?
The issue is coming from the new "negotiationEnabled" flag which is turned off by default now. Just do "directory.setNegotiationEnabled(true);" to enable it. When exposing static files that were generated like Javadocs, there is no need for content negotiation based on file extensions. First, that slows things down a bit and then it creates side-effects with inner class names like Router.Mode because "Mode" is not a recognized extension, etc. As for having multiple index base names I'm not sure yet because that complexifies things for now. If you really need this you can always setup additional DirectoryHandlers for a specific trees of files. > I'll post a link to the silly sample app in a few minutes. Thanks for > the updates! I'm looking forward to playing with it :-) Best regards, Jerome
