Hi Dominique,
Dominique Pfister wrote:
On 11/9/06, Pankaj Gupta (JIRA) [EMAIL PROTECTED] wrote:
[
http://issues.apache.org/jira/browse/JCR-623?page=comments#action_12448517
]
Pankaj Gupta commented on JCR-623:
--
Thanks for geting started on this
On 11/10/06, Ian Boston [EMAIL PROTECTED] wrote:
Will it be possible to replace FileJournal with something more message
oriented ?
eg JGroups or ActiveMQ (JMS Topic)
Yes, you can replace the FileJournal with another implementation of
the o.a.j.core.cluster.Journal interface that
Change resources sequence during transaction commit.
Key: JCR-631
URL: http://issues.apache.org/jira/browse/JCR-631
Project: Jackrabbit
Issue Type: Improvement
Affects Versions: 0.9,
[
http://issues.apache.org/jira/browse/JCR-631?page=comments#action_12448719 ]
Przemo Pakulski commented on JCR-631:
-
Sorry, i've made a mistake in first sentence. Should be :
It seems that during commmit of transaction first changes in
VersionManager lock not released in some circumstances
--
Key: JCR-632
URL: http://issues.apache.org/jira/browse/JCR-632
Project: Jackrabbit
Issue Type: Bug
Reporter: Przemo
Do you not mean the other way round? Currently first changes in the
workspace are committed, followed by changes in version storage?
On 11/10/06, Przemo Pakulski (JIRA) [EMAIL PROTECTED] wrote:
Change resources sequence during transaction commit.
Stefan Guggisberg wrote:
On 11/10/06, Tako Schotanus [EMAIL PROTECTED] wrote:
It's not very important, but is there a specific reason why the
CompactNodeTypeDefReader constructor takes a NamespaceMapping instead of
just a plain NamespaceResolver?
NamespaceResolver provides a 'read-only' view
On 11/10/06, Tako Schotanus [EMAIL PROTECTED] wrote:
Stefan Guggisberg wrote:
On 11/10/06, Tako Schotanus [EMAIL PROTECTED] wrote:
It's not very important, but is there a specific reason why the
CompactNodeTypeDefReader constructor takes a NamespaceMapping instead of
just a plain
DerbyPersistenceManager only usable for embedded databases
--
Key: JCR-633
URL: http://issues.apache.org/jira/browse/JCR-633
Project: Jackrabbit
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/JCR-633?page=all ]
Dominique Pfister resolved JCR-633.
---
Resolution: Fixed
Added a new configuration parameter to DerbyPersistenceManager named
shutdownOnClose; when set to true (the default), the database will
[
http://issues.apache.org/jira/browse/JCR-623?page=comments#action_12448792 ]
Dominique Pfister commented on JCR-623:
---
I quickly gained the impression, that creating a file for every journal record
could lead to serious problems because
Log / trace wrapper for the JCR API
Key: JCR-634
URL: http://issues.apache.org/jira/browse/JCR-634
Project: Jackrabbit
Issue Type: New Feature
Reporter: Thomas Mueller
I have implemented
[ http://issues.apache.org/jira/browse/JCR-634?page=all ]
Thomas Mueller updated JCR-634:
---
Attachment: jcrlog.zip
The source code
Log / trace wrapper for the JCR API
---
Key: JCR-634
13 matches
Mail list logo