Chetan Mehrotra wrote > > That being said then same argument can be applied to change being done > in Sling level where for same POST request now results in different > nodetypes being used. If that is a big concern then we can make use of > this new nodetype based on some request param. So a user would have to > specify that nodetype hint if he wants to use the oak:Resource > nodetype?
Which should be doable today - same would be true for oak:unstructured (vs nt:unstructured). So I think there is nothing to be done in Sling. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
