jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Douglass" <douglass.d...@gmail.com>
Subject Re: problem with imported multiple value properties
Date Thu, 17 Aug 2006 20:57:43 GMT
Well said, thanks for the explanation. Mine is a simple case, both due to
the data and that I know the rules by which to process it. But, as you say,
there is a more general problem that is much more difficult to solve.

On 8/17/06, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
> On 8/17/06, Doug Douglass <douglass.doug@gmail.com> wrote:
> > While it's easy enough to get around this issue for now, is there a
> specific
> > reason for the difference between system and document view roundtrip
> > support?
> It is impossible in the general case to detect whether a given XML
> attribute in document view should map to a single- or multivalued
> property. For example, if <foo bar="a b"/> maps to an nt:unstructured
> node "foo", should the "bar" property have a single value "a b" or a
> multiple values "a" and "b"?
> However, in many practical cases it will be possible to heuristically
> infer the correct interpretation or even a reasonable default, for
> example if "foo" maps to a custom node type that specifies "bar" as a
> single-valued string property. There's an ongoing effort to implement
> this (JCR-325), but the implementation is non-trivial and I haven't
> lately had too much time to focus on that.
> BR,
> Jukka Zitting
> --
> Yukatan - http://yukatan.fi/ - info@yukatan.fi
> Software craftsmanship, JCR consulting, and Java development

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message