Hi Ransford,
Am Mittwoch, den 01.08.2007, 13:46 -0700 schrieb paksegu:
> I have read the documention but I am still confuse on the purpose and benefit
> of sling, can you please give me a brief explanation of what is does and
> where it applicable, say a usecase scenario.
Basically, the intent
[
https://issues.apache.org/jira/browse/JCR-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517350
]
Antonio Carballo edited comment on JCR-1037 at 8/2/07 12:57 PM:
Our trace of the CacheM
[
https://issues.apache.org/jira/browse/JCR-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517350
]
Antonio Carballo edited comment on JCR-1037 at 8/2/07 12:38 PM:
Our trace of the CacheM
[
https://issues.apache.org/jira/browse/JCR-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Carballo updated JCR-1037:
--
Attachment: JCR-Trace.txt
Our trace of the CacheManager management of the memory pool.
> Memory
[
https://issues.apache.org/jira/browse/JCR-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517349
]
Antonio Carballo commented on JCR-1037:
---
We downloaded v1.3.1 sources and after debugging the CacheManager class
> Cris, thanks a lot for your comments: they helped me understand what
> Marcel's concerns are about the way Jackrabbit implements XA.
>
I think this is a good discussion to have in general. Marcel and I
both have some concerns, definitely - but I'm not yet sure they're
valid, as my points below s
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraic Hannon updated JCR-1050:
Attachment: JNDI_Datasource_Changes.diff
Diff file with non-synchronized JNDI datasources.
> Remove
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517311
]
Padraic Hannon commented on JCR-1050:
-
Yeah I saw that in the code. However, from what I can tell the only place wh
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen More reopened JCR-1049:
---
I am sorry, but IMO this does not seem like a reasonable solution.
Mysql fixed this bug ( not config ) as
Hi Cris,
On 8/2/07, Cris Daniluk <[EMAIL PROTECTED]> wrote:
> I've been observing this thread, pondering, and feel the need to weigh in.
>
Cris, thanks a lot for your comments: they helped me understand what
Marcel's concerns are about the way Jackrabbit implements XA.
> Marcel's point here is t
I've been observing this thread, pondering, and feel the need to weigh in.
Marcel's point here is that the JTA implementation doesn't allow the
RDBMS transaction to participate in the XA. I can see a good argument
for this - after all, Jackrabbit maintains an effective journal and
not all RDBMS ca
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-1049.
Resolution: Won't Fix
Assignee: Stefan Guggisberg
hi stephen,
thanks for reporting thi
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg updated JCR-1049:
---
Component/s: core
Summary: DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql
Hi,
Am Donnerstag, den 02.08.2007, 14:08 +0200 schrieb Angela Schreiber:
> Session.removeLockToken(String) on the session that
> created the lock. and subsequently:
> Session.addLockToken(String) on the other session, that
> should be the new lock holder.
Still the name set is the userID of the S
I am not actually sure, what you are referring to: Locking or
versioning. In case of Versioning, there is no lock owner, as checkout
only sets the checkedOut property. In case of Locking, the specification
is quite clear in section 8.4.4 Lock owner, that the lock owner is set
to the value of Ses
Hi,
> In this scenario if i checkout any node the lockowner is always the
> "superuser" i.e session.getUserId() .Is there a way to set the lockowner
> explicitly.
I am not actually sure, what you are referring to: Locking or
versioning. In case of Versioning, there is no lock owner, as checkout
Stefan Guggisberg wrote:
we just discovered, that the "orderable" attribute of node types is not
inherited from supertypes. NodeTypeImpl.hasOrderableChildNodes() just calls
NodeTypeDef.hasOrderableChildNodes() instead of using the EffectiveNodeType to
determine if a node type allows orderable ch
hi christoph
On 7/31/07, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> we just discovered, that the "orderable" attribute of node types is not
> inherited from supertypes. NodeTypeImpl.hasOrderableChildNodes() just calls
> NodeTypeDef.hasOrderableChildNodes() instead of using the EffectiveN
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517182
]
Dominique Pfister commented on JCR-1050:
I'm afraid, letting the application server manage the database connect
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit version 1.3.1. The release is available for download
at:
http://jackrabbit.apache.org/downloads.cgi
Release Notes -- Apache Jackrabbit -- Version 1.3.1
Introduction
Apache Jackrabbit is a fu
Hi,
I'm not sure if I understand this request for improvement.
> Using datasources
So you suggest to use DataSource.getConnection(..) instead of
DriverManager.getConnection(..)? How do you get / create the
datasource object, using JNDI? What about embedded applications where
JNDI is not availabl
21 matches
Mail list logo
