I agree with felix, /** - * @return an array of <code>Name</code>s representing the selector names of + * @return an array of <code>String</code>s representing the selector names of * the query result. * @see javax.jcr.query.QueryResult#getSelectorNames() */ - public Name[] getSelectorNames(); + public String[] getSelectorNames();
is not a backward compatible change! the problem is, that 2.3.7 can't be used now by any bundles that still need 2.4 and there is not stable 2.4 version. how about adding getSelectorJcrNames() and deprecate the other one? And if it can't be implemented, rather throw an UnsupportedException than changing the signature. regards, toby On Tue, Jan 24, 2012 at 4:00 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Wed, Jan 25, 2012 at 12:36 AM, Felix Meschberger <[email protected]> > wrote: >> I got a big problem with Jackrabbit SPI version 2.3.7 just released: This >> increases the >> export version of the org.apache.jackrabit.spi package from 2.4.0 to 3.0.0. > > Yes, I changed the SPI in a minor but backwards-incompatible way in > JCR-3198 (the QueryInfo.getSelectorNames signature was clearly wrong, > as selector names are opaque strings, not qualified names). Thus the > increase in the package version. > >> Consequence of this is, that I have a hard time updating the Sling DavEx >> bundle to this latest release ... > > What's the exact problem you're having? > > BR, > > Jukka Zitting
