one final comment is that using the existing dirlisting command, even
with all of these changes, is just a stepping stone for me. eventually
i'm going to make an export command that will place the parent node and
its child nodes in request attributes and then forward the request to
another uri - in this case a jsp which generates html that matches the
rest of my server's ui.
of course this means i'll have to extend the export context to carry the
servlet request and response, which is something tobias avoided in his
initial implementation, but i think there's a compelling reason to do it.
perhaps a compelling reason not to use the command-chains in
that particular case? ;)
regards
angela
