[
https://issues.apache.org/jira/browse/JCR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-765:
--
Attachment: statementclose.diff
simple patch that simply remove the logException() at statement cl
DatabasePersistenceManager: don't log exceptions for each statement when a
connection needs to be reestablished
---
Key: JCR-765
URL: https://issues.apache
PdfTextFilter may leave parsed document open in case of errors
--
Key: JCR-764
URL: https://issues.apache.org/jira/browse/JCR-764
Project: Jackrabbit
Issue Type: Bug
Affects Ver
[
https://issues.apache.org/jira/browse/JCR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-764:
--
Attachment: textfilter_close.diff
simple patch which adds an additional cleanup on exceptions.
>
hi,
Please vote on including those persistence managers to the Apache
Jackrabbit codebase. The vote is open for the next 72 hours, and only
votes from Jackrabbit committers are binding. The vote passes if at
least three +1 votes
and no vetos are cast.
The vote passes with 5 binding +1 votes an
[
https://issues.apache.org/jira/browse/JCR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Bloomfield Ramagem updated JCR-763:
--
Attachment: testservlet.war
Simple test Servlet for demonstrating the reported pro
[
https://issues.apache.org/jira/browse/JCR-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Bloomfield Ramagem updated JCR-763:
--
Attachment: stacktrace.txt
The stack trace from line 24 of TestServlet.java. This
On 2/23/07, Nicolas <[EMAIL PROTECTED]> wrote:
Hello,
I would like to propose a subject to the Jackrabbit community for Google
Summer Of Code 07.
Drawing on my experience from last year as a student, I would like to
propose a project where documentation is widely available and where no
update
Unable to create and login to different workspaces
--
Key: JCR-763
URL: https://issues.apache.org/jira/browse/JCR-763
Project: Jackrabbit
Issue Type: Bug
Components: jca
Affects V
Hello,
I would like to propose a subject to the Jackrabbit community for Google
Summer Of Code 07.
Drawing on my experience from last year as a student, I would like to
propose a project where documentation is widely available and where no
update to the core parts of Jackrabbit is needed. Besid
Is the SPI implementation supposed to ever throw a LockException,
definitely
or can it rely on the transient layer doing lock checks upfront?
that's a rhetoric question, right?
the spi impl must not rely on the client to behave properly.
but the client may cover some obvious cases (e.g. if
Angela Schreiber schrieb:
hi julian
(1) First of all, it leaves the question open whether an SPI
implementation actually needs to implement the locking semantics, or
whether *persisting* and *returning* the lock information is
sufficient. In any case, this should be documented well.
? what
hi julian
(1) First of all, it leaves the question open whether an SPI
implementation actually needs to implement the locking semantics, or
whether *persisting* and *returning* the lock information is sufficient.
In any case, this should be documented well.
? what do you mean?
(2) It seems
[
https://issues.apache.org/jira/browse/JCR-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475314
]
Jukka Zitting commented on JCR-762:
---
> where entry is object that represent xml structure with namespace
> "com.cisco
[
https://issues.apache.org/jira/browse/JCR-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-762.
---
Resolution: Fixed
Fixed in revisions 510905 and 510908.
Thanks for the problem report!
> System view
Hi,
I am using jcr2spi on top of a custom SPI implementation, and was trying
to come up with test cases that check the locking semantics (because I
know they weren't complete in my implementation).
After some testing I realized that JCR2SPI already does lock checking
locally (see ItemStateVa
16 matches
Mail list logo