-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> or would the jcr spec forbid it? found nothing about it. when
>> looking at the xml representation, it sounds totally normal. when
>> outputting i.e. the path of the property and the node it looks
>> strange.
>
> as of jcr 2.0 properties and child nodes may share the same namespace
> [0].
ok, thanks stefan. so this is to be expected.
that leaves the question about the invalid json in jsop. any inputs on this?
> ...
> now the json returned for /test looks like this:
>
> {"toast":"bar",":jcr:primaryType":"Name","jcr:primaryType":"nt:unstructured","toast":{}}
>
>
> note: there is twice the key "toast". as far as i understand json, this
> is not valid. the php function json_decode just overwrites the property
> "toast" => "bar" with the node array "toast" => array(). javascript json
> parsers tend to do the same.
>
> is jackrabbit using a custom json parser that can handle same-name keys?
> are there any plans to make this valid json?
>> [0] http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.4.2.2
>> Child Resolution
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9YhG4ACgkQqBnXnqWBgIun2QCgofJNqFReZ9d0w+isUoZkm/TO
M7AAnR3AccMtxD+bQryAhM+NUdmi57bZ
=PN3t
-----END PGP SIGNATURE-----
