My other q is why are some of the servlets implemented as JSP pages,
when, if you look into them, they are pretty much inline GET handlers in
the servlet.
-This adds an step to the build process and requires exactly the same
Jasper run time at the far end
-Doesnt appear to benefit the internals of the jsp pages much
In particular, pages like dfshealth.jsp look fairly complex inside (but
not as complex as happy_axis.jsp, my contribution to axis's health
checking [1]), but with very little formatting (and the omission of the
cache-content pragmas) it would seem to be cleaner and simpler to move
them into pure servlets inline.
Or is there a future plan to do more with JSP -in which case the pages
just need to be brought up to date with the right hadoop links and proxy
caching disabled.
-steve
[1] happyaxis.jsp:
http://svn.apache.org/viewvc/webservices/axis/trunk/java/webapps/axis/happyaxis.jsp?view=markup
-designed to diagnose the absence of axis.jar, hence is fully self
contained
-sets 500 on an error.
-forgets to set the no-cache options; doesnt work through a proxy
properly.
