I looked at the JCR 2.0 spec public review and it does not fix the issue. Do we have a chance to include such a sv:multivalued="true" marker for the 2.0 final?
Regards, Alex On Thu, Nov 20, 2008 at 6:09 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > On Thu, Nov 20, 2008 at 5:29 PM, Alessandro Bologna > <[EMAIL PROTECTED]> wrote: >> Maybe I am missing something, but if that's the case that I am not, maybe it >> would be worth adding some implementation specific workaround, such as >> adding an optional sv:multivalued="true" attribute that then can be used >> transparently during import. It should not break anything I believe (unless >> there's some strict validation of the SV schema in place). > > You're right, the spec is incomplete in that case and the only thing > we could do for now is to add some implementation-specific multivalue > marker. See also https://issues.apache.org/jira/browse/JCR-1464. > > BR, > > Jukka Zitting > -- Alexander Klimetschek [EMAIL PROTECTED]
