OutOfMemoryError when re-indexing the repository
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
[ http://issues.apache.org/jira/browse/JCR-550?page=3Dcomments#action_1=
2433037 ]=20
=20
Claus
Hi,
I think it's a good thing to do. Some random ideas:
I don't understand why it needs to be stateless (about my understanding of
stateless, see http://en.wikipedia.org/wiki/Stateless_server). As far as I
see stateless means it's slower, and I really don't like slow ;-) Even HTTP
is becoming
David,
Agreed regarding use of client and server as terminology - I think
this leads to some fuzzy thinking as the client and the application
that uses the client get confused.
Could we borrow from JDBC and call them the JCR Driver and JCR
Server? That to me gives the right sort of thinking in
I don't think so. This is actually restoring the node, so the current node is
overwritten with the older version. I just want to read the latest version
of a node before it was checked out.
In my application users are reading nodes, the checkedout state of a node
shouldn't be visable for the
Hi Thomas,
Thanks for your thoughtful comment.
I don't understand why it needs to be stateless (about my understanding of
stateless, see http://en.wikipedia.org/wiki/Stateless_server). As far as I
see stateless means it's slower, and I really don't like slow ;-) Even HTTP
is becoming more and
Hi J,
I think that your explanations point into the direction of multiple
workspaces. If user A has a workspace A that user can make
modifications in his workspace without user B in workspace B
can see the changes. As soon as user A checks something
into the version store user B can check it out
and ;) as marcel put it:
as a quick guideline: if you don't know how to achieve something ask on the
user list, if you think something is wrong and doesn't work as
expected use the dev list. Thank you.
Remove geronimo JTA as a runtime dependency
---
Key: JCR-564
URL: http://issues.apache.org/jira/browse/JCR-564
Project: Jackrabbit
Issue Type: Bug
Components: maven
Affects Versions:
[
http://issues.apache.org/jira/browse/JCR-564?page=comments#action_12433118 ]
Michael Neale commented on JCR-564:
---
OK, in maven 2 you can mark it as provided which means it is a compile/test
time dep, but at runtime it is expected to be
I'm posting here because at the moment I can't login to Jira (seems
my account was reset or something, and forgotten password seems to
send email by pigeon carrier).
I have a versioning bug in the presence of transactions. It's hard to
reproduce and seems memory-layout dependent.
At the
Hi,
On 9/7/06, Christophe Lombart [EMAIL PROTECTED] wrote:
what about the OCM Spring support ( in [Graffito trunk]/jcr/spring) ?
do you plan to move it into Jackrabbit ?
What do you see as the best option? It's tightly related to the OCM
tool so I think it would make sense to keep them
On 9/8/06, Jukka Zitting [EMAIL PROTECTED] wrote:
Hi,
On 9/7/06, Christophe Lombart [EMAIL PROTECTED] wrote:
what about the OCM Spring support ( in [Graffito trunk]/jcr/spring) ?
do you plan to move it into Jackrabbit ?
What do you see as the best option? It's tightly related to the OCM
tool
12 matches
Mail list logo
