jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Moseley <...@osafoundation.org>
Subject Re: problem with non-synchronized repository instances
Date Mon, 28 Mar 2005 20:02:38 GMT

for what it's worth, this turned out to be a classpath issue. jcr.jar 
was deployed into each webapp but was not visible to tomcat itself. i 
put it in $CATALINA_HOME/common/lib, and all is now good.

thanks for the help. hopefully this info will be useful to somebody in 
the future!

Brian Moseley wrote:
> Edgar Poce wrote:
>> A model 2 configuration example for Tomcat 4.x (see tomcat docs):
> ok, i used this configuration, configuring a global resource for the 
> repository factory and adding resource links to each of my webapps' 
> context config files (see below).
> the first webapp to be started by tomcat successfully looks up the 
> BindableRepository. great.
> however, the second webapp fails. the JNDI lookup appears to succeed, 
> but Spring throws a property conversion exception:
> org.springframework.beans.TypeMismatchException: Failed to convert 
> property value of type 
> [org.apache.jackrabbit.core.jndi.BindableRepository] to required type 
> [javax.jcr.Repository] for property 'repository'
> this is a Spring exception, so i'm going to ask about that on the Spring 
> list, but it sure seems like a bizarre problem, right? 
> BindableRepository implements Repository, after all.
> anyway, thanks for the pointers. using BindableRepository as the 
> resource type (which should have been obvious) was what i was missing. 
> now to figure out the Spring property conversion problem.

View raw message