Hi, Am Montag, den 31.12.2007, 17:07 +0100 schrieb Carsten Ziegeler: > Felix Meschberger wrote: > > > > Now, I do not understand anymore: You say, Jackrabbit is started > > embedded in Sling (using the jackrabbit-server bundle) but then you say, > > the RMI connection classes do not fit ?? > Hmm, did I say that? :)
Yes in message [1] you say: > The class is loaded correctly from the jcr api bundle - but it seems > that the > class coming from the rmi connection is loading differently. ;-) > > > > > Could it be, that you did not start Jackrabbit embedded but in a > > separate tomcat web app and you access it through the jackrabbit-client > > bundle ? Now, the question is, how the jackrabbit-client bundle loads > > the respective class. > > > Yes, I start jackrabbit as a separate webapp and access it through the > jackrabbit client bundle. The client bundle imports the jackrabbit api > classes from the jcr api bundle. And the jcr api bundle contains the > nodetypeloader class where the class cast exception occurs. This bundle > uses the jackrabbit classes that it contains. Are you sure, the jackrabbit-client is accessing the repository through RMI ? Could it be that it is accessing the JNDI stored resource ? In this latter case you get the actual Repository instance created by the other webapp. And this other instance uses a different node type loader class object as it does not seem to be shared by the two web apps. Regards Felix [1] http://www.mail-archive.com/[email protected]/msg01534.html
