I am using jcr2spi plus spi2dav at client side to access remote jcr repository.
However, when I tried to register new node types, I got following exception:
SEVERE: java.lang.UnsupportedOperationException: JCR-2003.
Implementation missing
java.lang.UnsupportedOperationException: JCR-2003.
Hi,
classes may explain HOW they work, but it's unclear for me which one is
the most appropriate one to use.
See http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ
Thanks Thomas. I saw this, too. But when browsing all the information on
the Wiki, I really get confused about
Gerald,
Guo Zhenhua wrote:
I am using jcr2spi plus spi2dav at client side to access remote jcr repository.
However, when I tried to register new node types, I got following exception:
SEVERE: java.lang.UnsupportedOperationException: JCR-2003.
Implementation missing
Hi,
I'm using Jackrabbit 2. Is the following scenario possible?
Node page = testRootNode.addNode(page);
page.addMixin(mix:versionable);
page.setProperty(name, 1);
page.setProperty(published, true);
session.save();
Hello JR users and developers!
Recently we have faced a problem with journalling that seems to resemble the
one reproduced in JCR-1846 (https://issues.apache.org/jira/browse/JCR-1846).
But that defect is closed and said to be fixed since 1.5.2, but we are using
1.5.5.
And in relation to
OK I have found the solution..
VersionHistory versionHistory =
session.getWorkspace().getVersionManager().getVersionHistory(page.getPath());
VersionIterator it = versionHistory.getAllVersions();
it.skip(1);
while ( it.hasNext()) {
On Mon, Dec 14, 2009 at 5:15 AM, Michael Dürig michael.due...@day.com wrote:
Gerald,
Guo Zhenhua wrote:
I am using jcr2spi plus spi2dav at client side to access remote jcr
repository.
However, when I tried to register new node types, I got following
exception:
SEVERE:
3) Is the Derby PM considered production worthy? Any reason not to use it?
Personal I trust derby as a low overhead database with zero
administration. It's not suitable if you have strong dba person which
she/he may lose job:) You may use other db if:
* Prepared to manage database.
* Multi
On 14 Dec 2009, at 13:24, ChadDavis wrote:
3) Is the Derby PM considered production worthy? Any reason not to use it?
Personal I trust derby as a low overhead database with zero
administration. It's not suitable if you have strong dba person which
she/he may lose job:) You may use other db
3) Is the Derby PM considered production worthy? Any reason not to use it?
Personal I trust derby as a low overhead database with zero
administration. It's not suitable if you have strong dba person which
she/he may lose job:) You may use other db if:
* Prepared to manage database.
* Multi
In the URL parameter, what is the create=true all about? Does this
refer to whether the DB schema is created on initialization, if it
doesn't already exist?
PersistenceManager
class=org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager
param name=url
On Dec 14, 2009, at 1:52 PM, ChadDavis chadmichaelda...@gmail.com
wrote:
3) Is the Derby PM considered production worthy? Any reason not
to use it?
Personal I trust derby as a low overhead database with zero
administration. It's not suitable if you have strong dba person
which
she/he
Yes, that is what that configuration parameter does.
Rakesh
On Dec 14, 2009, at 2:07 PM, ChadDavis chadmichaelda...@gmail.com
wrote:
In the URL parameter, what is the create=true all about? Does this
refer to whether the DB schema is created on initialization, if it
doesn't already exist?
On Mon, Dec 14, 2009 at 3:49 PM, Rakesh Vidyadharan rak...@sptci.comwrote:
On Dec 14, 2009, at 1:52 PM, ChadDavis chadmichaelda...@gmail.com wrote:
3) Is the Derby PM considered production worthy? Any reason not to use
it?
Personal I trust derby as a low overhead database with zero
On Mon, Dec 14, 2009 at 8:07 PM, ChadDavis chadmichaelda...@gmail.com wrote:
In the URL parameter, what is the create=true all about? Does this
refer to whether the DB schema is created on initialization, if it
doesn't already exist?
It's a derby parameter to create db if the db does not
On Mon, Dec 14, 2009 at 7:24 PM, ChadDavis chadmichaelda...@gmail.com wrote:
What do you mean that the embedded db can only have a single
connection? If I run my repository in some server fashion, such as
RMI or SPI, can I still connect to the repository from two
Jackrabbit session share the
On Mon, Dec 14, 2009 at 3:25 PM, Guo Du mrdu...@gmail.com wrote:
On Mon, Dec 14, 2009 at 8:07 PM, ChadDavis chadmichaelda...@gmail.com wrote:
In the URL parameter, what is the create=true all about? Does this
refer to whether the DB schema is created on initialization, if it
doesn't already
+1
On Fri, Dec 4, 2009 at 2:29 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Thu, Dec 3, 2009 at 11:28 PM, Samuel Cox crankydi...@gmail.com wrote:
I'm unaware of anything outside of what is published from the Jackrabbit
site (this mailing list). Does anyone else know of anything
I try to build a repository including 7 million data(no binaries), now I've
store 1.3m data, but I got an error, and then I can't start the repository.
I set the log4j level to debug, and see that the calendar index of one node
indexed failed when start the repository.
I use
I want to register new node types and add new nodes into jackrabbit
repository. I use the default credential.
I got following exception:
javax.jcr.AccessDeniedException: Access denied
at
20 matches
Mail list logo
