Felix Meschberger wrote: > Hi Carsten, > > Am Freitag, den 28.12.2007, 11:51 +0000 schrieb [EMAIL PROTECTED]: >> Use reflection to check for method of jackrabbit node type manager as the >> instanceof is failing in some cases. >> This is a workaround until the real problem has been found/solved. > > Hmm, the only reason I could think of why the instanceof check would > fail, if the interface class object (JackrabbitNodeTypeManager) used in > the instaneceof check is not the same as the interface class object > referred to by the runtime class of the ntm object being checked. > Yes, it seems that this is the problem - unfortunately I was not yet able to tell where the different classes are coming from.
> This is a serious problem and hints at some classloading and declaration > issues. Yepp. > > Are you seeing this when running Sling as a web application in a Servlet > Container having the Jackrabbit API classes in a shared (e.g. container) > class loader ? Could it be that Sling is thus not using the serlvet > container provided class but the one provided by the jcr/api bundle ? > I'm running Sling in Tomcat - the jackrabbit api classes are not shared - as far as I can tell from debugging, Sling is using the one provided by the api bundle. But I have no idea where the other class is coming from. The sling webapp has only one jackrabbit api set in the classpath (through the osgi bundle). Perhaps its some classloader magic by Tomcat? Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
