Winston WOLFF wrote:
> So my current thinking is to have a separate site map or index which
> upon startup will walk through the directory tree and find all the
> servlet files. It will then call each one and use
> callMethodOfServlet() to get it's author, title, what sub-pages it
> connects to, subject, and keywords. Has anybody developed similar
I've done something very similar to what you are suggesting, in my case for
a Help feature that contains an index of the servlets. It enumerates the
servlets and uses callMethodOfServlet() to get the title of each servlet.
It works quite well; the only gotcha is that I use a number of PSP's which
individually don't take very long to compile, but if you hit the Help
servlet before having hit the individual PSP's, then that triggers the
compilation of ALL of the PSPs at once, because callMethodOfServlet() is
called on all of them. As a result, that first request to the Help servlet
is very slow. My solution was just to access the Help servlet after
starting up the app server, to get everything compiled and cached.