What about a totally different approach. My main problems with some of the suggestions are:
a) we have to fix a lot of places (post servlet, webdav, other modules creating files), creating duplicate code. If this is made configurable, then its even more of a nightmare. b) oak:resource is not a node type defined in the spec I understand that changing nt:resource might be a problem - although this might be more a theoretical one. Obviously the preferred solution is to do it in a single place, which leads to changing it in Oak or having some way to do it via Oak - instead of changing several places above Oak in the application layer. The easiest solution that comes to my mind is: Whenever a nt:resource child node of a nt:file node is created, it is silently changed to oak:resource. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
