[
https://issues.apache.org/jira/browse/JCR-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839913#action_12839913
]
Frederic Guilbeault commented on JCR-2525:
--
Proposed solution would be to introduce
NodeState and NodeStateListener deadlock
Key: JCR-2525
URL: https://issues.apache.org/jira/browse/JCR-2525
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
[
https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839877#action_12839877
]
johann sorel commented on JCR-1697:
---
"GQL" has no relation with JCR. it is just a candidate
[
https://issues.apache.org/jira/browse/JCR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839871#action_12839871
]
Alexander Klimetschek commented on JCR-1248:
> A query like this will fail:
> //
[
https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839864#action_12839864
]
Paco Avila commented on JCR-1697:
-
Another option is to handle these kind of queries internal
[
https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839860#action_12839860
]
Paco Avila commented on JCR-1697:
-
The GQL.execute() returns a RowIterator and would be nice
[
https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839855#action_12839855
]
Marcel Reutegger commented on JCR-2524:
---
Forgot to mention that the proposed patch redu
[
https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2524:
--
Status: Patch Available (was: Open)
> Reduce memory usage of DocIds
> --
[
https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2524:
--
Attachment: JCR-2524.patch
Proposed patch.
> Reduce memory usage of DocIds
> ---
[
https://issues.apache.org/jira/browse/JCR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839819#action_12839819
]
Paco Avila edited comment on JCR-1248 at 3/1/10 7:38 PM:
-
A query lik
[
https://issues.apache.org/jira/browse/JCR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839819#action_12839819
]
Paco Avila commented on JCR-1248:
-
A query like this will fail:
//element(*, nt:base)[jcr:co
On Mon, Mar 1, 2010 at 14:42, Thomas Müller wrote:
>> Couldn't this be done by a special wrapping Repository implementation?
>
> That's problematic. Such a wrapper would have quite some overhead. The
> JCR API is not easily "wrapable" if you want to do it correctly: you
> would have to wrap almost
[
https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839717#action_12839717
]
Marcel Reutegger commented on JCR-2524:
---
Some memory stats from a real life system: a f
Reduce memory usage of DocIds
-
Key: JCR-2524
URL: https://issues.apache.org/jira/browse/JCR-2524
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core
Re
StaleItemStateException during distributed transaction
--
Key: JCR-2523
URL: https://issues.apache.org/jira/browse/JCR-2523
Project: Jackrabbit Content Repository
Issue Type: Bug
Hi,
Currently Jackrabbit doesn't support relayed initialization. Unless I
misunderstood Felix, he would also like to get rid of this
restriction.
Just to clarify: my suggestion is *not* about requiring the repository
is initialized when the first session is opened. It's also *not* about
requiring
On Mon, Mar 1, 2010 at 11:50, Thomas Müller wrote:
> String factoryClass = "...";
> String url = "...?user=sa&password=xyz";
> RepositoryFactory factory = (RepositoryFactory)
> Class.forName(factoryClass).newInstance();
> Map parameters = new HashMap();
> parameters.put("url", url);
> Repository r
Hi,
-1 on defining this on this isolated level.
This should be part of a broader concept of how to architect/structure
JR3 and its backend connections.
Regards
Felix
On 28.02.2010 16:40, Thomas Müller wrote:
> Currently Jackrabbit initializes the repository storage (persistence
> manager) when
On Sun, Feb 28, 2010 at 16:41, Thomas Müller wrote:
> == Use Error Codes ==
>
> Currently exception message are hardcoded (in English). When using
> error codes, exception messages could be translated. I'm not saying we
> should translate them ourselves, but if somebody wants to, he could.
>
> ==
On Mon, Mar 1, 2010 at 10:50 AM, Thomas Müller wrote:
> Currently, Jackrabbit requires to be able to create a database
> connection when initializing.
I was thought like this too :)
> It depends on what you mean with "repository level". It doesn't make
> sense to store the user name and password
Dominique Pfister wrote:
I wouldn't call it error code, then: every time something changes
either in the calling code or in the code throwing the exception,
you'll get a different hash code.
Agreed, the stack trace might be too unstable. But I still like the idea
of using something cryptic for
Hi,
> I am not clear what credentials you are refering to
I refer to the database user name and password that are currently
stored in the repository.xml (except when using JNDI):
http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/persistence/bundle/BundleDbPersistenceManager.html
#
On Mon, Mar 1, 2010 at 9:32 AM, Michael Dürig wrote:
> What about using something like a hash code (for example of the current
> stack trace) as error code? These would then automatically serve as hash
A good sample to deal with error messages:
http://publib.boulder.ibm.com/infocenter/ltscnnct/v2
I wouldn't call it error code, then: every time something changes
either in the calling code or in the code throwing the exception,
you'll get a different hash code.
Dominique
On Mon, Mar 1, 2010 at 10:32 AM, Michael Dürig wrote:
>> == Use Error Codes ==
>
> What about using something like a has
On Mon, Mar 1, 2010 at 5:41 AM, Thomas Müller wrote:
> The question is: should Jackrabbit 3 *require* (like now) that the
> credentials for the storage are included in the repository
> configuration? I think for some storage backends it should not require
> that. Instead (only in those cases), it
== Use Error Codes ==
What about using something like a hash code (for example of the current
stack trace) as error code? These would then automatically serve as hash
tags for Google searches. That is, errors pasted into a discussion forum
would be indexed by Google. Searching for 'Error
6df
26 matches
Mail list logo
