jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: jsop and property / node with same name
Date Thu, 08 Mar 2012 12:38:44 GMT
On 2012-03-08 11:58, Angela Schreiber wrote:
> ...
> imo the same-name-property-node feature was a bad move in jsr 283
> and i don't see a particular value in having this feature.
> ...

I thought it was in JSR 170 already.

> some time ago i was chatting with julian about possibilities
> to distinguish properties and nodes in the jcr-remoting but
> we never really invested sufficient time to address this.
>
> as far as jsop is concerned i don't remember that we ever
> talked about this problematic. but you may come up with a
> suggestion on how to address this.

Essentially we need a well-defined mapping between a JCR node hierarchy 
and JSON; right now there are edge case that IMHO break.

> without a having a closer look i can think of
> a - no supported at all (there is an repository descriptor for
> this called: OPTION_NODE_AND_PROPERTY_WITH_SAME_NAME_SUPPORTED)
> -> fix jcr-server not to return this descriptor and not
> to allow for same-named node/property siblings
> b - supported by ignore the fact that it isn't valid json
> c - invent some extra marker for properties that have the same
> name as a sibling node.
> and there are for sure many other options if this really turns out
> to be a problem.
>
> b was for free, a was rather cheap. right now with all the
> jackrabbit3 effort i wouldn't invest a lot of time in c.
>
> but it's definitely worth to keep this in mind for later
> JSOP discussions in order not to forget to address this once
> we have a more formal and finalized protocol.
> ...

Indeed!

Mime
View raw message