Yeah, you may be right out it's usefulness, but on the video I watched, it was being pitched as a performance boost if you had a massive web app (with annotations and web-fragments). So the use case would be, develop the app with annotations enabled and in production, switch them off and use the master (generated) web.xml, that's what my understanding of it was. So, with that in mind, I'd have thought a web.xml file would have been created and that could be checked into version control without the user having to do anything.
This may not be what had been envisioned for it's primary use, it just struck me as a nice feature to have. On 15 July 2011 22:18, Jesse Farinacci <jie...@gmail.com> wrote: > Greetings, > > On Fri, Jul 15, 2011 at 5:10 PM, Stephen Munro > <stephen.ross.mu...@gmail.com> wrote: > > Thanks for the quick reply! I've got it working, so thanks. I'm a little > > curious why the web-app structure is dumped directly to the logs rather > than > > have it written to a .xml for convenience say...web-generated.xml? > > Great! The configuration option name has "log" right in it. I wouldn't > expect it to do anything other than log the effective web.xml. Having > this effective web.xml output to a special file seems of limited > value, you can simply copy and paste in the rare event that you > actually require it. > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Warmest Regards, Stephen Munro
