[ http://issues.apache.org/jira/browse/JCR-165?page=comments#action_12320533 ]
Tobias Strasser commented on JCR-165: ------------------------------------- sound arguments :-) after reviewing the code i came to the same conclusion, that a major restructuration is needed in order to handle the export (import) more sophisticated. on a first thought, the object-oriented way, transfering the responsibility to the resource was obvious. but now i think, this should be handled on a more global level. i think there are several steps involved: - locating the resource (i.e. url -> path mapping) - identifying the resource (collection, non-collection) - finding the respective action-handler (GET, PUT, MKCOL, etc..) - executing the action - responding to the client (did i miss some?) > add ability to ignore specific node types when generating webdav directory > listing > ---------------------------------------------------------------------------------- > > Key: JCR-165 > URL: http://issues.apache.org/jira/browse/JCR-165 > Project: Jackrabbit > Type: Improvement > Versions: 1.0 > Reporter: Brian Moseley > Priority: Minor > Attachments: dirlisting.patch > > attached is a patch that enhances DirListingExportCommand to allow specific > node types to be ignored when generating the html directory listing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
