angela (JIRA) wrote:
thanks for the patch. i think it would be a useful enhancement to provide means
to filter certain items. however, i have the impression that this involves more
than just the dirlisting, e.g. the response to a propfind request.
yes. i made a change to that effect in my local copy of jcr-server.
fwiw, i also made a change that lets me define additional node types
that are not collections for the purposes of DavResource.isCollection().
second i think it would be better to filter by the nodetype that defines a
given item, rather than filter by the nodetype of a given node.
i'm not sure exactly what you mean.
and last but not least one possibly want to hide items with a given name.
absolutely.
we are currently thinking about such an enhancement as well and will keep you
informed.
great!
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.
