Hi Thomas,
We encountered the exact same problem. I did some unit tests, and the
org.textmining.text.extraction.WordExtractor does not work very well.
As you described, it omits whole sections of documents (apparently
triggered by certain formatting fields present in the document).
I noticed in
El mié, 07-06-2006 a las 17:12 +0200, Tobias Bocanegra escribió:
> > So, I need to checking() just after save(). I thinks this is a strange
> > behavior.
>
> well, if you create a new node, and it would be checked-in right away,
> you could not write anything to itand that's how it is specifie
[ http://issues.apache.org/jira/browse/JCR-452?page=all ]
Stefan Guggisberg resolved JCR-452:
---
Resolution: Fixed
fixed in svn r412428
> Workspace.clone throws ItemNotFoundException on a referenceable node with
> children
> --
So, I need to checking() just after save(). I thinks this is a strange
behavior.
well, if you create a new node, and it would be checked-in right away,
you could not write anything to itand that's how it is specified
by jsr170.
regards, toby
On 6/7/06, Paco Avila <[EMAIL PROTECTED]> wrote:
El mié, 07-06-2006 a las 11:06 +0200, Tobias Bocanegra escribió:
> when you create a new versionable node, it is in a checked-out state,
> until you explicitely check-in the node. so Node.isCheckedOut should
> always return true, until you checkin the node.
So, I need to checking() just after save
[ http://issues.apache.org/jira/browse/JCR-454?page=all ]
Marcel Reutegger reassigned JCR-454:
Assign To: Marcel Reutegger
> Query with document order fails when result set size > caching hierarchy
> manager size
> --
[ http://issues.apache.org/jira/browse/JCR-454?page=all ]
Marcel Reutegger updated JCR-454:
-
Attachment: CachingHmgrTest.java
Test case to reproduce issue.
> Query with document order fails when result set size > caching hierarchy
> manager size
>
Hi Stefan,
this seems to be a bug in jackrabbit. I was able to reproduce it with a
small test case and created a jira issue.
See: http://issues.apache.org/jira/browse/JCR-454
you can avoid this bug by disabling the document order on the query
result. well, you tried that already but the name
Query with document order fails when result set size > caching hierarchy
manager size
-
Key: JCR-454
URL: http://issues.apache.org/jira/browse/JCR-454
Project: Jackrabbit
Type: Bug
[ http://issues.apache.org/jira/browse/JCR-453?page=all ]
Tobias Bocanegra closed JCR-453:
Fix Version: 1.1
Resolution: Fixed
fixed.
Committed revision 412344.
> add/remove dispatchers from DelegatingObservationDispatcher is not
> synchroniz
when you create a new versionable node, it is in a checked-out state,
until you explicitely check-in the node. so Node.isCheckedOut should
always return true, until you checkin the node.
regards, toby
On 6/6/06, Paco Avila <[EMAIL PROTECTED]> wrote:
When I add a new versionable node, the node i
[ http://issues.apache.org/jira/browse/JCR-453?page=all ]
Tobias Bocanegra reassigned JCR-453:
Assign To: Tobias Bocanegra
> add/remove dispatchers from DelegatingObservationDispatcher is not
> synchronized
>
add/remove dispatchers from DelegatingObservationDispatcher is not synchronized
---
Key: JCR-453
URL: http://issues.apache.org/jira/browse/JCR-453
Project: Jackrabbit
Type: Bug
Environment:
[
http://issues.apache.org/jira/browse/JCR-452?page=comments#action_12415101 ]
Tobias Bocanegra commented on JCR-452:
--
this seems to be the same as: JCR-439
> Workspace.clone throws ItemNotFoundException on a referenceable node with
> children
> -
[ http://issues.apache.org/jira/browse/JCR-452?page=all ]
Stefan Guggisberg reassigned JCR-452:
-
Assign To: Stefan Guggisberg
> Workspace.clone throws ItemNotFoundException on a referenceable node with
> children
> --
Here is a sample code:
-
import java.io.File;
import java.io.IOException;
import java.util.Calendar;
import java.util.Hashtable;
import javax.jcr.Node;
import javax.jcr.Repository;
import javax.jcr.Session;
import javax.jcr.SimpleCredentials;
import jav
16 matches
Mail list logo
