well, then you could put something that is not even phpcr-odm as a child. but well...

what if the media document would be AbstractFile? is that class doing something that we do not want? i think it already provides the hierarchy stuff and such things.

one tricky issue i realize is that using nt:folder restricts the children of the folder to only be nt:file - you can't add anything else under a folder. so if we want to go full through, media would need to be of type nt:file and could for example put the external information into its jcr:content child node (not using nt:resource, which is not required). otherwise we probably should drop using nt:folder and the Folder class. which would have the drawback that people can't use webdav anymore when using jackrabbit...

sorry for the confusion. i think we need to be radical in one way or the other. either its all in the nt:folder / nt:file logic to work with webdav and be clean. or we ditch that notion again and are fully flexible on what one can put into the repository. eventually we could offer both sets of documents, a strict webdav-y one and a flexible lax one.