Hi,
> No particular reason. I didn't know that the others were better.
> What are the differences between the three?
I have updated the PersistenceManagerFAQ in the Wiki:
http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ
The information there is still incomplete, but the bundle persistenc
[
https://issues.apache.org/jira/browse/JCR-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529020
]
Stefan Guggisberg commented on JCR-935:
---
> Esteban Franqueiro commented on JCR-935:
>
hi thomas,
just for clarification ..
you sayed that one disadvantage of the ObjectPersistenceManager
is the non transational behaviour
there was a lot of discussion about transactions in jackrabbit and
the statement that i get from this discussion is that jackrabbit "itself" (the
session) is t
Hi,
On 9/20/07, KÖLL Claus <[EMAIL PROTECTED]> wrote:
> so my opinion is it should be regardless which peristence manager you use
> jackrabbit should be always transactional if a operation runs inside a
> transaction
> context. is this true or not ?
You need to have a persistence manager that ca
Hi,
Maybe 'non transactional' is the wrong expression. Such persistence
managers (for example the ObjectPersistenceManager) usually work OK,
you can use transactions in Jackrabbit and so on, the exception is
'atomicy' in a crash. When the process is stopped while a transaction
is persisted (power
Hi ,
do you know when the patch will be committed and
whether it is safe to use BundleBDPersistenceManager and
BundleFsPersistenceManager
as they are at the moment until this issue is resolved ?
Thank you,
Savvas
On 5/31/07, Przemo Pakulski (JIRA) <[EMAIL PROTECTED]> wrote:
>
>
> [
> https
Hi,
On 9/20/07, ruchi goel <[EMAIL PROTECTED]> wrote:
> Yes, we are deeply interested in an interim release since we were
> dependent on Graffito's OCM layer earlier. Now since it is part of
> Jackrabbit , we will be depending on a Jackrabbit release to be
> bundled in our product.
Unfortunatel
Hi,
On 9/20/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Given the growth of the number of more or less independent "top-level
> sub-projects" in Jackrabbit, we should probably start again thinking of
> having independent releases ?
>
> For example, I could imagine, that OCM has definitely a
[
https://issues.apache.org/jira/browse/JCR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529077
]
Martijn Hendriks commented on JCR-940:
--
Hi Thomas,
I think that besides the BundleDbPM.store method the
Connectio
[
https://issues.apache.org/jira/browse/JCR-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1034:
---
Affects Version/s: 0.9
1.0
1.0.1
1.
[
https://issues.apache.org/jira/browse/JCR-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1128:
---
Fix Version/s: (was: 1.4)
1.3.2
Merged to the 1.3 branch in revision 577696.
>
[
https://issues.apache.org/jira/browse/JCR-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-774:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1090:
---
Affects Version/s: 0.9
1.0
1.0.1
1.
[
https://issues.apache.org/jira/browse/JCR-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1008:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
Hi,
> I think that besides the BundleDbPM.store method
> the ConnectionrecoveryManager.execute* methods
> also need to be wrapped by a retry-loop.
I think you are right, those methods should loop as well (except when
autoReconnect is false).
> I've patched this locally and want to execute the un
[
https://issues.apache.org/jira/browse/JCR-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-862:
--
Affects Version/s: 1.2.1
1.2.2
1.3
1.3
Hi Jukka,
You have also commented out setAutoCommit(true):
--- BundleDbPersistenceManager
con = DriverManager.getConnection(url, user, password);
-con.setAutoCommit(true);
+//con.setAutoCommit(true);
In my view this line can be completely removed, as by default
autoCommit
Hi,
On 9/20/07, Thomas Mueller <[EMAIL PROTECTED]> wrote:
> I have multiple configurations (copies of the applications/test
> directory). Before running the build I just replace the files with the
> configuration (simple db, bundle db, data store) I want to test. I
> think it would be great if the
Hi,
On 9/20/07, Thomas Mueller <[EMAIL PROTECTED]> wrote:
> You have also commented out setAutoCommit(true):
>
> --- BundleDbPersistenceManager
> con = DriverManager.getConnection(url, user, password);
> -con.setAutoCommit(true);
> +//con.setAutoCommit(true);
Hmm, that's c
> I'm about to start working on the release plans for both Jackrabbit
> 1.3.2 and 1.4. I'll start by identifying issues in Jira to
> target releases, and will follow up with more detailed
> release plans for both releases later this week.
>
> The 1.3.2 release will be a patch release from the 1.
LockOperation - In a clustered environment, a lock created on one server is not
sent to the other servers.
--
Key: JCR-1141
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/JCR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting reassigned JCR-564:
-
Assignee: Jukka Zitting
> Remove geronimo JTA as a runtime dependency
>
[
https://issues.apache.org/jira/browse/JCR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-564:
--
Attachment: jta.patch
Interesting, we actually had an existing issue for the change that was recently
dis
[
https://issues.apache.org/jira/browse/JCR-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1038:
---
Affects Version/s: 0.9
1.0
1.0.1
1.
[
https://issues.apache.org/jira/browse/JCR-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-813:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-812:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1071:
---
Affects Version/s: (was: 1.4)
1.3
1.3.1
Fix Ve
[
https://issues.apache.org/jira/browse/JCR-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1051:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1055:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529166
]
Jukka Zitting commented on JCR-862:
---
Additional merges in revisions 577729 and 577831.
> unsynchronized access on 'it
[
https://issues.apache.org/jira/browse/JCR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-905:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1092:
---
Affects Version/s: 1.3
Fix Version/s: (was: 1.4)
1.3.2
Merged to the
[
https://issues.apache.org/jira/browse/JCR-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1039:
---
Affects Version/s: 1.3
Fix Version/s: (was: 1.4)
1.3.2
Merged to the
[
https://issues.apache.org/jira/browse/JCR-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-811:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-884:
--
Affects Version/s: 1.2.1
1.2.2
1.2.3
1
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1049:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1065:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1068:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1069:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1074:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1078:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1076:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1081:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1082:
---
Fix Version/s: 1.3.2
Merged to the 1.3 branch in revision 577864.
> cache getting out of sync with tra
[
https://issues.apache.org/jira/browse/JCR-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1083:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1088:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1095:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1096:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1101:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1110:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1109:
---
Affects Version/s: 1.1
1.1.1
1.2.1
[
https://issues.apache.org/jira/browse/JCR-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1120:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1121:
---
Affects Version/s: 1.2.1
1.2.2
1.2.3
[
https://issues.apache.org/jira/browse/JCR-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-832:
--
Fix Version/s: 1.3.2
Affects Version/s: 1.3.1
> BundleDBPersistenceManager does not free blobStore
[
https://issues.apache.org/jira/browse/JCR-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1048.
Resolution: Won't Fix
Assignee: Jukka Zitting
Resolving as Won't Fix based on the above rationa
Hi,
On 9/20/07, Esteban Franqueiro <[EMAIL PROTECTED]> wrote:
> I would start by suggesting including the revisions that contain the
> fixes for JCR-862 (already commited by Jukka), JCR-962, JCR-978 and
> JCR-1082.
Thanks for the suggestions! JCR-862 and JCR-1082 are easy additions,
but JCR-962 a
Hil all,
I'm going to start the OCM project reorganization.
Do you have some commits to do in this subproject ?
I'm still looking for a solution to run the same unit tests with the
different mapper impl (digester, annotations, ...). This is not so easy if
we want to support java 1.4 because the o
[
https://issues.apache.org/jira/browse/JCR-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529247
]
Jukka Zitting commented on JCR-832:
---
Toby or Przemo, are you planning to act on this in near future? If not, I'll
tak
Hi,
This is my plan for the 1.3.2 release of Apache Jackrabbit. The
purpose of this release is to push out a number of bug fixes before
the 1.4 release is ready. No new features or other improvements will
be included in this release.
I've already started preparing the release by creating a 1.3.2
Will you also consider including JCR-978, similar to JCR-962 ?
-Original Message-
From: Jukka Zitting [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 5:25 PM
To: dev@jackrabbit.apache.org
Subject: Apache Jackrabbit 1.3.2 release plan
Hi,
This is my plan for the 1.3.2 releas
Hi,
I've now started the Jira component restructuring that was discussed
some time ago.
As a first step I've renamed some of the main components in Jira to
match the Maven artifactIds (and folder names) of the respective
components in svn. The changes are:
Jackrabbit API -> jackrabbit-api
Hi,
On 9/20/07, Pablo Rios <[EMAIL PROTECTED]> wrote:
> Will you also consider including JCR-978, similar to JCR-962 ?
Yes. I typically don't include improvement issues in patch releases,
but JCR-978 seems to be a prerequisite for JCR-962. So if we decide to
include JCR-962 then I guess we need t
OK, thank you.
-Original Message-
From: Jukka Zitting [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 5:47 PM
To: dev@jackrabbit.apache.org
Subject: Re: Apache Jackrabbit 1.3.2 release plan
Hi,
On 9/20/07, Pablo Rios <[EMAIL PROTECTED]> wrote:
> Will you also consider inclu
Hi Thomas,
> > I've patched this locally and want to execute the unit
> tests using the MSSQL bundle PM. I'm not familiar with the
> test harness...how should I do this? Some initial attempts to
> alter the repository.xml and workspace.xmls in the
> jackrabbit-core\applications\test directory
64 matches
Mail list logo
