So as I dig into the jackrabbit jars a bit further I realize that they have a
lot of servlets that can do the things we're looking for: start up a local
repository, connect to a local or remote repository, expose the webdav
interface etc.
I'm thinking it might be best to remove the container
I have just read the entire thread in Nabble. If I have well understood we
can't any longer override the widget.verbose property (from a web.xml file
or the context) if it's set to true. Isn't that a development functionnal
regression for the convenience of one (business?) person?
If we really
I'm thinking we don't need a Jackrabbit component. All we need is a factory for
javax.jcr.Repository, and that could be put in the content component. The
factory will try to find a repository via JNDI, and if that fails, use Java's
SPI to find a javax.jcr.Repository instance (which would return
On 12/07/2010, at 4:04 AM, Adrian Crum wrote:
I'm thinking we don't need a Jackrabbit component. All we need is a factory
for javax.jcr.Repository, and that could be put in the content component.
I would really prefer to not mix components for a couple of reasons:
- Some of the existing
[
https://issues.apache.org/jira/browse/OFBIZ-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12887238#action_12887238
]
BJ Freeman commented on OFBIZ-3852:
---
Thanks Hans, for the clarification.
I also read that
--- On Sun, 7/11/10, Scott Gray scott.g...@hotwaxmedia.com wrote:
On 12/07/2010, at 4:04 AM, Adrian
Crum wrote:
I'm thinking we don't need a Jackrabbit component. All
we need is a factory for javax.jcr.Repository, and that
could be put in the content component.
I would really prefer to
On 12/07/2010, at 11:33 AM, Adrian Crum wrote:
--- On Sun, 7/11/10, Scott Gray scott.g...@hotwaxmedia.com wrote:
On 12/07/2010, at 4:04 AM, Adrian
Crum wrote:
The factory will try to find a repository via JNDI,
and if that fails, use Java's SPI to find a
javax.jcr.Repository instance
