I was thinking of following the same principle that the ServiceStatus page uses, which is to only be displayed when not in production mode.
On Thu, Jun 25, 2009 at 10:16, Ben Gidley <b...@gidley.co.uk> wrote: > I think this is useful - maybe you should include it as a component so we > can add it an appropriately private area of our > sites. It is in general a bad idea to leave such pages on in > production - but they are handy for development or as protected > diagnostic pages. > > Ben Gidley > > www.gidley.co.uk > b...@gidley.co.uk > > > On Thu, Jun 25, 2009 at 10:04 AM, Hugo Palma <hugo.m.pa...@gmail.com> > wrote: > > > I've created an application status page that it's very similar to the > > service status that is bunbled with the framework but instead of showing > > information on services it shows information on the web application > itself. > > > > You can check out the code for it and a screenshot here > > > http://hugopalma.wordpress.com/2009/06/24/tapestry-application-status-page/ > > > > I would also like to know if you guys think that such a page should be > > included in the framework itself. If so i'll gladly create the issue and > > appropriate patch. > > > > Cheers, > > Hugo > > >
