On Thu, Aug 27, 2009 at 8:33 AM, Peter Chiochetti<[email protected]> wrote: > Am 2009-08-25 14:54, schrieb Alexander Klimetschek: >> >> So setting :name should "force" the post servlet to do 1. only. If it >> behaves differently, it's a bug. > > Well, then I have found a bug. Sorry, I cannot provide a patch. Will you > care to make this an issue? > > Steps to reproduce, in a recent svn launchpad build (about 2 weeks old): > > curl -F"title=NewNode" http://.../content/N > ==> Content created /content/N > > curl -F"title=UpdateNode" http://.../content/N > ==> Content modified /content/N > > curl -F"title=NewNode" -F":nameHint=N" http://.../content/* > ==> Content created /content/n > > curl -F"title=Bug!" -F":name=N" http://.../content/* > ==> Content created /content/N_0
Yes, looks like a bug. As Bertrand noted, you can create an issue at http://issues.apache.org/jira/browse/SLING, it's ok to provide the above test case as plain text. And we are always happy about a broad range of contributors, including bug reports! Regarding the issue: it might be related that there is a property "title" set, which in case of a non-existing :name property should be used as a node name hint. Maybe this (erroneously) forces the code to see the :name as a hint... just a guess, though. Regards, Alex -- Alexander Klimetschek [email protected]
