I think I finally found it, still not sure as I'm getting an error I
got earlier but got rid of and has now returned on both of my servlets.
I'm now getting this
ava.lang.ClassCastException:
org.apache.jackrabbit.core.jndi.BindableRepository
com.vms.adsite.util.WebDAVUtils.getRepo(WebDAVUtils.java:20)
com.vms.adsite.webDAV.WebDAVServlet.getRepository(WebDAVServlet.java:
12)
org
.apache
.jackrabbit
.webdav
.simple
.SimpleWebdavServlet.getDavSessionProvider(SimpleWebdavServlet.java:
317)
org
.apache
.jackrabbit
.webdav
.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:204)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
Which I know is related to not having the jar files in the common/lib
folder. Here are the jar files I have in there:
jcr-1.0-api
jackrabbit-api-1.4
jackrabbit-core-1.4
jackrabbit-jcr-commons-1.4
jackrabbit-spi-1.4
jackrabbit-spi-commons-1.4
jackrabbit-text-extractors-.1.4
slf4j-log4j-12-1.3.0
slf4j-api-1.3.0
log4j-1.2.13
If there are other jar files that need to go in there let me know (or
if they should be in different directories (like server/shared or
something) let me know.
Thanks.
-warner
On Aug 28, 2008, at 1:28 AM, Alexander Klimetschek wrote:
On Thu, Aug 28, 2008 at 1:47 AM, Warner Onstine
<[EMAIL PROTECTED]> wrote:
Ok, I have now setup my repo as outlined here:
http://jackrabbit.apache.org/shared-j2ee-resource-howto.html
I have one webapp that has setup the repo for access through
WebDAV. I have
another application that only needs read-only access to the repo.
The WebDAV
seems to be working just fine, but the second webapp has constantly
been
having problems gaining access to the repo.
I am getting this error:
org.apache.naming.NamingContext lookup
WARNING: Unexpected exception resolving reference
javax.jcr.RepositoryException: The repository home /Users/warnero/
test-repo
appears to be in use since the file named .lock is locked by another
process.
This means that another Jackrabbit instances is still running and
using the same repository home directory, which is not possible, hence
this lock mechanism. Maybe you have another JVM with j2ee or
Jackrabbit configured? Or accidentally configured two Jackrabbits in
your container?
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
