Hi, I happen to agree with Eric. Lets not artificially criple this feature; I think it is implemented rather simply by calling into the importer framework.
As it happens, I actually once used the XML import support for round-tripping of our very own XML export support in the Default Get Servlet. So, even if we would drop ZIP and JAR, we should keep XML for roundtripping with the Default GET Servlet. Regards Felx Am 10.01.2012 um 17:10 schrieb Eric Norman: > I'm not sure I see any benefit of doing that. What do you gain by limiting > the import to json only? There is no additional work to support the other > import formats. > > One other data point: From the users mailing list, there is at least one > person importing using the jcr.xml format (see: > http://markmail.org/message/p5nfmk7b5qcvnr7f ) so I don't think it is > correct to assume no one is using the other import formats. > > Regards, > Eric > > On Tue, Jan 10, 2012 at 7:30 AM, Carsten Ziegeler <[email protected]>wrote: > >> Hi, >> >> currently the sling post servlet uses our content importer for >> importing. This has basically been added to post json. >> However the content importer handles other files like xml, zip, and >> jar as well. But I really think we should support this and concentrate >> on one format, just json. (Reducing this is easy). >> >> If noone objects, I'll implement this change >> >> Thanks >> Carsten >> >> -- >> Carsten Ziegeler >> [email protected] >>
