Justin Edelson schrieb: > On 2/11/10 1:33 PM, Ian Boston wrote: >> On 11 Feb 2010, at 16:06, Justin Edelson wrote: >> >>> This, combined with the use of the JCR 2 bundle, is causing some test >>> failures. It seems to be because AccessControlUtil.getAccessManager() >>> attempts to call the getAccessManager() method specified by the >>> javax.jcr.Session interface which isn't implemented by SessionImpl. >>> >>> Possible fixes are: >>> * Upgrade jackrabbit.server to JR 2. >>> * Remove NamespaceMapper modifications to jcr.base and roll back to old >>> jcr.api bundle in launchpad. >>> >>> WDYT? >> IMHO remove NamespaceMapper, however I think I saw a commit from Carsten >> that added an NamespaceMapper class into one of the APIs (and versioned to >> 2.1.0) ? >> > Right. jcr.api now exports version 2.1.0 of org.apache.sling.jcr.api. > Changes to this module need not be rolled back because, with or without > the inclusion of NamespaceMapper in the API, the jcr.api bundle can't be > used without either a wrapped JCR 1 API bundle or the JCR 2 API bundle. > I think we should just update to jcr 2.
Carsten -- Carsten Ziegeler [email protected]
