Hi,
After disabling the known issue tests I know of, there are still two
test failures being reported. I don't know what is causing them or
when they have appeared. Could someone with more intimate versioning
code knowledge check if these are regressions or known issues?
Testcase: testRemoveVers
Hi,
On 7/7/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Question to any JUnit gurus out there: Is there a standard way or a
best practice for creating unit tests for known issues for which no
immediate fix is expected?
Thanks for all the comments! I ended up solving the issue with system
prope
Hi,
On 7/19/06, Nicolas <[EMAIL PROTECTED]> wrote:
SizeException will be raised when the BackupIOHandler will have a size of
more than the size parameter. I am not sure yet if I will keep it. What do
you think?
OK. I'm not sure if there's really a use case for the maximum file
size option, i.e
SizeException will be raised when the BackupIOHandler will have a size of
more than the size parameter. I am not sure yet if I will keep it. What do
you think?
Sure for your other points.
Nicolas
On 7/19/06, Jukka Zitting (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://issues.apache.org/jira/b
[
http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12422233 ]
Jukka Zitting commented on JCR-442:
---
Committed patch-backup-060719.txt in revision 423575.
Some issues to consider:
* The SizeException and RepositoryConfigBackup
[ http://issues.apache.org/jira/browse/JCR-299?page=all ]
Jukka Zitting resolved JCR-299.
---
Resolution: Fixed
Assignee: Jukka Zitting
Fixed in revision 423547 by catching and logging all index filter exceptions
(even unchecked ones). After considerin
[ http://issues.apache.org/jira/browse/JCR-442?page=all ]
Nicolas Toper updated JCR-442:
--
Attachment: patch-backup-060719.txt
Patch for the backup tool:
1/ Parsing of the configuration file is over
2/ Instanciation of the backup manager
3/ First draft of t
[ http://issues.apache.org/jira/browse/JCR-299?page=all ]
Jukka Zitting updated JCR-299:
--
Affects Version/s: 1.0.1
Priority: Minor (was: Major)
> errors in text filters can cause indexing to fail without warning the client
> --
[ http://issues.apache.org/jira/browse/JCR-483?page=all ]
Stefan Guggisberg resolved JCR-483.
---
Resolution: Fixed
fixed in svn rev. 423488
> Lock tokens reains in session after unlock
> --
>
> Key
[
http://issues.apache.org/jira/browse/JCR-483?page=comments#action_12422169 ]
Stefan Guggisberg commented on JCR-483:
---
the spec doesn't mention whether Node.unlock() should remove the token from the
session.
intuitively i'd agree with yo
[ http://issues.apache.org/jira/browse/JCR-483?page=all ]
Stefan Guggisberg updated JCR-483:
--
Issue Type: Improvement (was: Bug)
Priority: Minor (was: Major)
correcting type and priority
> Lock tokens reains in session after unlock
> --
[ http://issues.apache.org/jira/browse/JCR-483?page=all ]
Stefan Guggisberg reassigned JCR-483:
-
Assignee: Stefan Guggisberg
> Lock tokens reains in session after unlock
> --
>
> Key: JCR-483
>
but, it's defined as string:
[nt:frozenNode] > mix:referenceable
orderable
- jcr:frozenPrimaryType (name) mandatory autocreated protected abort
- jcr:frozenMixinTypes (name) protected multiple abort
- jcr:frozenUuid (string) mandatory autocreated protected abort
- * (undefined) protected abo
[
http://issues.apache.org/jira/browse/JCR-476?page=comments#action_12422136 ]
Stefan Guggisberg commented on JCR-476:
---
there are some minor javadoc issues with the QNameCache class which could be
easily fixed
once the patch has been com
[ http://issues.apache.org/jira/browse/JCR-482?page=all ]
Jukka Zitting updated JCR-482:
--
Fix Version/s: 1.1
Affects Version/s: 0.9
1.0
1.0.1
(was: 1.1)
Good point.
The spec r
Hi,
The spec says that jcr:frozenUuid is a STRING but jackrabbit 1.0.1
uses a REFERENCE for it.
Is it an oversight?
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
hi paco,
you're right. there's indeed excessive access control checking.
i committed a fix that should improve the situation considerably
(svn rev 423448).
thanks for reporting this issue,
cheers
stefan
On 7/19/06, Paco Avila <[EMAIL PROTECTED]> wrote:
I'm implementing muy own AccessManager and
Vishaal Kant hyperion.com> writes:
>
> Where can I find examples of Jackrabbit Search API usage examples??
>
> My requirement is to achieve search using wild characters.
>
> I wanted to search my repository on the basis of Wild characters. I have
> add files to my repository, I am trying to u
unable to do checkin/checkout operations from Dreamweaver 8.
Key: JCR-484
URL: http://issues.apache.org/jira/browse/JCR-484
Project: Jackrabbit
Issue Type: Improvement
Co
Lock tokens reains in session after unlock
--
Key: JCR-483
URL: http://issues.apache.org/jira/browse/JCR-483
Project: Jackrabbit
Issue Type: Bug
Components: locks
Affects Versions: 1.0.1
Hi,
On 7/19/06, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
i will try to adjust the css so that it works with the old logo until
the deisgner modified the new one.
I just contacted the PRC asking for more detailed logo guidelines.
I'll report back when I find out more.
BR,
Jukka Zitting
--
I'm implementing muy own AccessManager and I've seen that there are lots
of READ access when I perform a node.save() after adding a new child
node.
You can see it in the attachment access_log.txt. Sample code is provided
in Dummy.java, and repository config in repository2.xml.
--
Paco Avila <[
well, legal sux :-)
As part of the website upgrade, someone decided to change the ASF logo.
As you might imagine, making arbitrary changes to the Apache logos are
just as forbidden here as they would be for any other company.
that is understandable. however, the designed singed all legal
docume
23 matches
Mail list logo
