unsubscribe
unsubscribe
Re: About FileDataStore mod-time update
You are right, lastAccessTime() isn't included until Java 7 :( http://openjdk.java.net/projects/nio/javadoc/java/nio/file/attribute/BasicFileAttributes.html#lastAccessTime%28%29 On Thu, Oct 13, 2011 at 8:22 AM, Thomas Mueller wrote: > Hi, > > > Why don't check the "access time", instead of using the "modification > time" for this? At least in UNIX / Linux you can check when a file was > accesed last time. > > First of all, in Java you can't. Second, many file systems don't update > that value. > > Regards, > Thomas > > -- OpenKM http://www.openkm.com
Re: About FileDataStore mod-time update
Why don't check the "access time", instead of using the "modification time" for this? At least in UNIX / Linux you can check when a file was accesed last time. On Wed, Oct 12, 2011 at 1:42 PM, Thomas Mueller wrote: > Hi, > > > I think we should drop support for multiple distinct repositories > > > Removing features from existing classes is problematic... What about a > config option or a new class where this isn't supported. > > >The upside would be that with > >something like that we'd be able to avoid the troublesome need to > >update the last access timestamp whenever a record is accessed. > > We don't do that currently. It's only done when garbage collection is run. > > Regards, > Thomas > > -- OpenKM http://www.openkm.com
Re: About FileDataStore mod-time update
On Wed, Oct 12, 2011 at 10:22 AM, Thomas Mueller wrote: > Hi, > > > This means that every time a file is accessed is like has been modified > and this is not true. > > When garbage collection is running, yes. > I don't understand why the file mod-time need to be updated when DataStoreGarbageCollector is running. What is the sense of this? > > incremental backups does not make sense > > If incremental backup only checks the last modified time, then it's a > problem, I agree. However I'm afraid I don't know a better way to solve the > problem (mark the file as still being used). Suggestions are always welcome > of course. > > Is it possible that the incremental backup checks the file creation time > instead of the last modification time? > Well, the modification time check has the meaning of when the file was modified (of course) and the backup application need to know if a file has been modified, because the file creation time should no be modified during the existence of the file. rsync, for example can be configured to avoid the mod-time comparison and use a checksum-based comparison algorithm. But not all the backup application are so configurable :( > > Regards, > Thomas > > -- OpenKM http://www.openkm.com
About FileDataStore mod-time update
Hi there. I'm curious about the behabior of the FileDataStore.getRecordIfStored(DataIdentifier identifier) method: when access a DataRecord, it update the modification time of the file. This means that every time a file is accessed is like has been modified and this is not true. The main reason of this questions os the backup of the Jacrabbit DataStore: incremental backups does not make sense because the these kind of aplications check the file mod-time to see if has been modified, and always are modified in my case because I run a DataStoreGarbageCollector every nigth and this process update the mod-time of every file in the DataDatore. Thanks in advance. -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: what we have to use instead of Query.XPATH
Thanks for the info.
On Thu, Jul 7, 2011 at 5:51 PM, Alexander Klimetschek wrote:
> On 07.07.11 17:41, "Paco Avila" wrote:
>
> I'm also interested in this question. Which alternative is proposed by JCR
> 2.0 ?
>
>
> JCR 2.0 provides JCR-SQL2 or better AQM (abstract query model) on top of
> which one should be able to implement any kind of query language. The idea
> was that instead of specifying one or multiple specific query language
> syntaxes (upon which it seems is hard to agree ;-)), it would be better to
> specify the search semantics using an abstract query tree (as object model
> in this case). JCR –SQL2 is one ootb "serialization" of that tree.
>
> The implementation in Jackrabbit currently does not (yet!?) reflect that
> approach. The "old" Xpath & JCR-SQL languages are implemented as before, and
> there is a new & somewhat separate query engine for JCR-SQL2 and the AQM
> (however I am not up to date with the latest improvements in that area).
>
> Once this new engine is fast enough, it might make sense to build an Xpath
> to AQM converter (as well as JCR-SQL to AQM) and provide that as something
> like a jcr-search-commons utility library for use on top of the JCR API. But
> that's just one idea.
>
> Cheers,
> Alex
>
>
>
> On Thu, Jul 7, 2011 at 5:38 PM, Alexander Klimetschek
> wrote:
>
>> It is only deprecated in the JCR 2.0 spec (and hence the javax.jcr api
>> docs), but Jackrabbit will continue to support it, since a lot of apps on
>> top of Jackrabbit make use of Xpath as the primary query language.
>>
>> Cheers,
>> Alex
>>
>> On 07.07.11 08:21, "g. raaja" wrote:
>>
>> >Hi,
>> >
>> >Its showing Query.XPATH is deprecated and in API its showing
>> >
>> >*Deprecated. As of JCR 2.0, this language is deprecated.*
>> >
>> >my code is: This is for adding spellcheck
>> >
>> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
>> >Query query =
>>
>> >qm.createQuery("/jcr:root[rep:spellcheck('"+content+"')]/(rep:spellcheck()
>> >)",
>> >Query.XPATH);*
>> >
>> >and in another condition
>> >
>> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
>> >stmt1 ="//element(*,nt:resource)[jcr:contains(.,'"+content+"')]";
>> >Query q = qm.createQuery(stmt1, Query.XPATH)*;
>> >
>> >I am not getting an idea what I have to use instead of this.
>> >
>> >Please guide me what to use in the place of this Query.XPATH.
>> >
>> >Thanking you.
>> >
>> >--raaja g
>> >
>> >--
>> >View this message in context:
>> >
>> http://jackrabbit.510166.n4.nabble.com/what-we-have-to-use-instead-of-Quer
>> >y-XPATH-tp3650763p3650763.html
>> >Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>> >
>>
>>
>>
>> --
>> Alexander Klimetschek
>> Developer // Adobe (Day) // Berlin - Basel
>>
>>
>
>
> --
> OpenKM
> http://www.openkm.com
> http://www.guia-ubuntu.org
>
>
>
>
> --
> Alexander Klimetschek
> Developer // Adobe (Day) // Berlin - Basel
>
--
OpenKM
http://www.openkm.com
Re: what we have to use instead of Query.XPATH
I'm also interested in this question. Which alternative is proposed by JCR
2.0 ?
On Thu, Jul 7, 2011 at 5:38 PM, Alexander Klimetschek wrote:
> It is only deprecated in the JCR 2.0 spec (and hence the javax.jcr api
> docs), but Jackrabbit will continue to support it, since a lot of apps on
> top of Jackrabbit make use of Xpath as the primary query language.
>
> Cheers,
> Alex
>
> On 07.07.11 08:21, "g. raaja" wrote:
>
> >Hi,
> >
> >Its showing Query.XPATH is deprecated and in API its showing
> >
> >*Deprecated. As of JCR 2.0, this language is deprecated.*
> >
> >my code is: This is for adding spellcheck
> >
> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
> >Query query =
> >qm.createQuery("/jcr:root[rep:spellcheck('"+content+"')]/(rep:spellcheck()
> >)",
> >Query.XPATH);*
> >
> >and in another condition
> >
> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
> >stmt1 ="//element(*,nt:resource)[jcr:contains(.,'"+content+"')]";
> >Query q = qm.createQuery(stmt1, Query.XPATH)*;
> >
> >I am not getting an idea what I have to use instead of this.
> >
> >Please guide me what to use in the place of this Query.XPATH.
> >
> >Thanking you.
> >
> >--raaja g
> >
> >--
> >View this message in context:
> >
> http://jackrabbit.510166.n4.nabble.com/what-we-have-to-use-instead-of-Quer
> >y-XPATH-tp3650763p3650763.html
> >Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
> >
>
>
>
> --
> Alexander Klimetschek
> Developer // Adobe (Day) // Berlin - Basel
>
>
--
OpenKM
http://www.openkm.com
http://www.guia-ubuntu.org
Re: what we have to use instead of Query.XPATH
I'm also interested in this question. Which alternative is proposed by JCR
2.0 ?
On Thu, Jul 7, 2011 at 5:38 PM, Alexander Klimetschek wrote:
> It is only deprecated in the JCR 2.0 spec (and hence the javax.jcr api
> docs), but Jackrabbit will continue to support it, since a lot of apps on
> top of Jackrabbit make use of Xpath as the primary query language.
>
> Cheers,
> Alex
>
> On 07.07.11 08:21, "g. raaja" wrote:
>
> >Hi,
> >
> >Its showing Query.XPATH is deprecated and in API its showing
> >
> >*Deprecated. As of JCR 2.0, this language is deprecated.*
> >
> >my code is: This is for adding spellcheck
> >
> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
> >Query query =
> >qm.createQuery("/jcr:root[rep:spellcheck('"+content+"')]/(rep:spellcheck()
> >)",
> >Query.XPATH);*
> >
> >and in another condition
> >
> >*QueryManager qm = jcrSession.getWorkspace().getQueryManager();
> >stmt1 ="//element(*,nt:resource)[jcr:contains(.,'"+content+"')]";
> >Query q = qm.createQuery(stmt1, Query.XPATH)*;
> >
> >I am not getting an idea what I have to use instead of this.
> >
> >Please guide me what to use in the place of this Query.XPATH.
> >
> >Thanking you.
> >
> >--raaja g
> >
> >--
> >View this message in context:
> >
> http://jackrabbit.510166.n4.nabble.com/what-we-have-to-use-instead-of-Quer
> >y-XPATH-tp3650763p3650763.html
> >Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
> >
>
>
>
> --
> Alexander Klimetschek
> Developer // Adobe (Day) // Berlin - Basel
>
>
--
OpenKM
http://www.openkm.com
Re: End of life for Jackrabbit 1.x
Ups! time to schedule an upgrade :) On Tue, Jun 7, 2011 at 7:43 PM, Jukka Zitting wrote: > Hi, > > The 1.6 branch is soon two years old (1.6.0 was released in August > 2009) and I don't see us doing any more patch releases against it. > Thus I'd like to officially declare the end of life of Jackrabbit 1.x > and encourage all our remaining 1.x users to upgrade. > > Unless someone still wants to keep Jackrabbit 1.x alive, I'll drop the > 1.6.x releases from the download page and announce the end of life > status to the users@ list in a few weeks. > > BR, > > Jukka Zitting > -- OpenKM http://www.openkm.com
Re: [j3] Repository MicroKernel API draft
Interesting... I expect to have a couple of hours to give a try. El 11/05/2011 18:31, "Stefan Guggisberg" escribió:
[jira] [Commented] (JCR-2873) Add a way to locate full text extraction problems
[ https://issues.apache.org/jira/browse/JCR-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010795#comment-13010795 ] Paco Avila commented on JCR-2873: - Great, I was missing this feature for years! At least, now I can see which document were not indexed. Is also possible to make a relation between the document and the text extraction error? > Add a way to locate full text extraction problems > - > > Key: JCR-2873 > URL: https://issues.apache.org/jira/browse/JCR-2873 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: indexing, jackrabbit-core >Reporter: Jukka Zitting >Assignee: Jukka Zitting >Priority: Minor > Fix For: 2.3.0 > > > Full text indexing of a binary document can fail for various reasons. > Currently we just log a generic error message in such cases, which makes it > difficult for the user to locate such problems for review and reindexing. We > should improve this by making the logs more informative or by adding some > other mechanism for locating troublesome documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-2873) Add a way to locate full text extraction problems
[ https://issues.apache.org/jira/browse/JCR-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010786#comment-13010786 ] Paco Avila commented on JCR-2873: - So if I search for "TextExtractionError" should return all the binary properties which failed to be indexed? > Add a way to locate full text extraction problems > - > > Key: JCR-2873 > URL: https://issues.apache.org/jira/browse/JCR-2873 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: indexing, jackrabbit-core >Reporter: Jukka Zitting >Assignee: Jukka Zitting >Priority: Minor > Fix For: 2.3.0 > > > Full text indexing of a binary document can fail for various reasons. > Currently we just log a generic error message in such cases, which makes it > difficult for the user to locate such problems for review and reindexing. We > should improve this by making the logs more informative or by adding some > other mechanism for locating troublesome documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jackrabbit performance results
In the graphs, less is supposed to be better? On Fri, Oct 8, 2010 at 10:26 AM, Jukka Zitting wrote: > Hi, > > The Jackrabbit performance suite we recently added has proved quite > useful, so I wanted to share full performance report from last night: > > http://people.apache.org/~jukka/jackrabbit/20101008/report.html > > See [1] for the exact definitions of these test cases. New test cases > or improvements to the existing ones are very much welcome, just like > patches that optimize Jackrabbit performance! > > [1] http://svn.apache.org/repos/asf/jackrabbit/trunk/test/performance/base/src/main/java/org/apache/jackrabbit/performance/ > > BR, > > Jukka Zitting > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: [VOTE] Release Apache Jackrabbit 1.6.4
+1 On Wed, Oct 6, 2010 at 7:56 PM, Jukka Zitting wrote: > Hi, > > A candidate for the Jackrabbit 1.6.4 release is available at: > > http://people.apache.org/~jukka/jackrabbit/1.6.4/ > > The release candidate is a zip archive of the sources in: > > http://svn.apache.org/repos/asf/jackrabbit/tags/1.6.4/ > > The SHA1 checksum of the archive is e5362fce7adb148dd17cbd413899f11f78424fb8. > > A staged Maven repository is available for review at: > > https://repository.apache.org/content/repositories/orgapachejackrabbit-004/ > > Please vote on releasing this package as Apache Jackrabbit 1.6.4. The > vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit 1.6.4 > [ ] -1 Do not release this package because... > > Here's my +1. > > BR, > > Jukka Zitting > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: Jackrabbit 1.6.4 release plan
Great! On Mon, Oct 4, 2010 at 1:00 PM, Jukka Zitting wrote: > Hi, > > Given the interest to a 1.6.4 release, I'll cut the release candidate > on Wednesday this week after checking the issue tracker for any > pending issues. > > BR, > > Jukka Zitting > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: When is planned the 1.6.4 release?
Would be nice. On Thu, Sep 30, 2010 at 5:29 PM, Tom Quellenberg wrote: > Is there a chance to integrate JCR-2546 into 1.6.4? > We observed the same problem in the 1.6 branch and could provide a patch for > 1.6.x > > Regards, > Tom > > > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: When is planned the 1.6.4 release?
I use 1.6.1 because of JCR-2656 which I see is solved in 1.6.4, so would be nice a release :) On Thu, Sep 30, 2010 at 3:25 PM, Tom Quellenberg wrote: > Hi, > > we are still using the 1.6 branch and would appreciate a new 1.6.4 release > very much. > > Regards, > Tom > > > - Ursprüngliche Mail - >> I think also we can start to realease it. >> >> greets >> claus >> >> -Ursprüngliche Nachricht- >> Von: Jukka Zitting [mailto:jukka.zitt...@gmail.com] >> Gesendet: Donnerstag, 30. September 2010 14:59 >> An: dev@jackrabbit.apache.org >> Betreff: Re: When is planned the 1.6.4 release? >> >> Hi, >> >> On Thu, Sep 30, 2010 at 1:42 PM, Paco Avila wrote: >> > I have seen that all issues are resolved, so when is planned the >> > release? >> >> I guess we can do the release right away if there's demand. I kind of >> put the 1.6 branch on hold after the lack of too much interest in the >> 1.6.3 release [1,2]. >> >> [1] http://markmail.org/message/mtp7ou6xdd2tka6l >> [2] http://markmail.org/message/yup4bqdq6zeijc5g >> >> BR, >> >> Jukka Zitting > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
When is planned the 1.6.4 release?
I have seen that all issues are resolved, so when is planned the release? Regard.s -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
[jira] Commented: (JCR-2656) Embedded Derby fails under JBoss because of JMX-related conflicts
[ https://issues.apache.org/jira/browse/JCR-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897790#action_12897790 ] Paco Avila commented on JCR-2656: - So, how can use Jackrabbit 1.6.2 under JBoss? > Embedded Derby fails under JBoss because of JMX-related conflicts > - > > Key: JCR-2656 > URL: https://issues.apache.org/jira/browse/JCR-2656 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core >Affects Versions: 1.6.2 > Environment: Linux Ubuntu 10.04 LTS >Reporter: Paco Avila > > JBoss fails to start due to a bug in Derby-10.4.2.0. The dependency should be > agains derby-10.4.2.1 which seems to has this bug fixed. More info at > https://issues.apache.org/jira/browse/DERBY-3887 > Please, include this fix in the upcoming 1.6.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-2659) Fails to remove a previously assigned mixin
Fails to remove a previously assigned mixin --- Key: JCR-2659 URL: https://issues.apache.org/jira/browse/JCR-2659 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 1.6.2 Environment: Linux Ubuntu 10.04 LTS Reporter: Paco Avila Fix For: 1.6.3 Jackrabbit fails to remove a previously assigned mixin. Works fine on version 1.6.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2656) Embedded Derby fails under JBoss because of JMX-related conflicts
[ https://issues.apache.org/jira/browse/JCR-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-2656: Fix Version/s: 1.6.3 > Embedded Derby fails under JBoss because of JMX-related conflicts > - > > Key: JCR-2656 > URL: https://issues.apache.org/jira/browse/JCR-2656 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core >Affects Versions: 1.6.2 > Environment: Linux Ubuntu 10.04 LTS >Reporter: Paco Avila > Fix For: 1.6.3 > > > JBoss fails to start due to a bug in Derby-10.4.2.0. The dependency should be > agains derby-10.4.2.1 which seems to has this bug fixed. More info at > https://issues.apache.org/jira/browse/DERBY-3887 > Please, include this fix in the upcoming 1.6.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-2656) Embedded Derby fails under JBoss because of JMX-related conflicts
Embedded Derby fails under JBoss because of JMX-related conflicts - Key: JCR-2656 URL: https://issues.apache.org/jira/browse/JCR-2656 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 1.6.2 Environment: Linux Ubuntu 10.04 LTS Reporter: Paco Avila JBoss fails to start due to a bug in Derby-10.4.2.0. The dependency should be agains derby-10.4.2.1 which seems to has this bug fixed. More info at https://issues.apache.org/jira/browse/DERBY-3887 Please, include this fix in the upcoming 1.6.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Jackrabbit 1.6.2
+1 On Tue, Jun 1, 2010 at 1:52 PM, Jukka Zitting wrote: > Hi, > > I've posted a candidate for the Jackrabbit 1.6.2 release to: > > http://people.apache.org/~jukka/jackrabbit/1.6.2/ > > The release candidate is a jar archive of the sources in: > > http://svn.apache.org/repos/asf/jackrabbit/tags/1.6.2/ > > The SHA1 checksum of the archive is 1b6830aa877783a704fd626b7b01982b65ac1515. > > A staged Maven repository of the release is available at: > > https://repository.apache.org/content/repositories/orgapachejackrabbit-027/ > > Please vote on releasing this package as Apache Jackrabbit 1.6.2. The > vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit 1.6.2 > [ ] -1 Do not release this package because... > > Here's my +1. > > BR, > > Jukka Zitting > > > Release Notes -- Apache Jackrabbit -- Version 1.6.2 > > Introduction > > > Apache Jackrabbit 1.6.2 is a bug fix release that fixes issues reported > against previous releases. This release is backwards-compatible with the > earlier 1.6.x releases, but contains a change in persistence format that > makes it impossible to downgrade to an earlier release after a repository > has been upgraded to the 1.6.2 version. A full backup of the repository > is recommended before this upgrade. > > Changes in this release > --- > > This release fixes the following issues: > > JCR-2170 Remove PropDefId and NodeDefId > JCR-2433 NPE when copying nodes with Workspace.copy() > JCR-2456 Repository is corrupt after concurrent changes with the same session > JCR-2503 inconsistent session and persistent state after ... > JCR-2525 NodeState and NodeStateListener deadlock > JCR-2554 Deadlock inside XASession on Weblogic > JCR-2577 SISM.checkAddedChildNodes() prevents merging of concurrent changes > JCR-2611 DefaultHighlighter.java does not encode illegal XML characters > JCR-2613 NoSuchItemStateException on checkin after removeVersion in XA ... > JCR-2645 XML text extraction in Jackrabbit 1.x accesses external resources > > See the Jackrabbit issue tracker for more details about these changes: > > https://issues.apache.org/jira/browse/JCR > > The issue tracker also documents all the known issues in this release. > > Release Contents > > > This release consists of a single source archive packaged as a zip file. > The archive can be unpacked with the jar tool from your JDK installation. > See the README.txt file for instructions on how to build this release. > > The source archive is accompanied by SHA1 and MD5 checksums and a PGP > signature that you can use to verify the authenticity of your download. > The public key used for the PGP signature can be found at > https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS. > > Contributors > > > The following people have contributed to this release by submitting bug > reports or by participating in the issue resolution process. > > Antonio Martinez Marcel Reutegger Stefan Guggisberg > Bart van der Schans Martijn Hendriks Stephan Huttenhuis > Bram de Kruijff Maxime Bégnis The Dong > Claus Köll Paul Jara Thomas Müller > Frederic Guilbeault Peter Krokavec Tobias Bocanegra > Grégory Joseph Robert Sauer Tom Quellenberg > Jukka Zitting Sascha Theves > > Thank you to everyone involved! > > About Apache Jackrabbit > --- > > Apache Jackrabbit is a fully conforming implementation of the Content > Repository for Java Technology API (JCR, specified in JSR 170 and 283). > > A content repository is a hierarchical content store with support for > structured and unstructured content, full text search, versioning, > transactions, observation, and more. > > For more information, visit http://jackrabbit.apache.org/ > > About The Apache Software Foundation > > > Established in 1999, The Apache Software Foundation provides organizational, > legal, and financial support for more than 100 freely-available, > collaboratively-developed Open Source projects. The pragmatic Apache License > enables individual and commercial users to easily deploy Apache software; > the Foundation's intellectual property framework limits the legal exposure > of its 2,500+ contributors. > > For more information, visit http://www.apache.org/ > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: Jackrabbit 1.6.2 release plan
JCR-2456 fix in 1.6.2 would be pretty nice :) On Tue, Apr 27, 2010 at 5:02 PM, Bart van der Schans wrote: > Hi Jukka, > > On Tue, Apr 27, 2010 at 4:26 PM, Jukka Zitting > wrote: >> Hi, >> >> On Tue, Apr 13, 2010 at 6:20 PM, Jukka Zitting >> wrote: >>> Please respond here or use the 1.6.2 tag in Jira to mark any issues >>> you'd like to see included in this release. I'd like to target late >>> April (i.e. about two weeks from now) for the release date. >> >> We now have the following fixes in the 1.6 branch: >> >> JCR-2433 NPE when copying nodes with Workspace.copy() >> JCR-2525 NodeState and NodeStateListener deadlock >> JCR-2554 Deadlock inside XASession on Weblogic >> JCR-2611 DefaultHighlighter.java does not encode illegal XML characters >> JCR-2613 NoSuchItemStateException on checkin after removeVersion in XA ... >> >> Unless anyone asks for more fixes to be backported, I'll cut the 1.6.2 >> release candidate tomorrow. > > We could check if we need to address "JCR-2456: Repository is corrupt > after concurrent changes with the same session" in the 1.6 branch. > > Regards, > Bart > > >> >> BR, >> >> Jukka Zitting >> > > > > -- > Hippo B.V. - Amsterdam > Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 > > Hippo USA Inc. - San Francisco > 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 > - > http://www.onehippo.com - i...@onehippo.com > - > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: Document Management System
Yes, an OpenKM also is based ontop Jackrabbit. On Wed, Mar 31, 2010 at 2:37 PM, Dhrubo wrote: > Yes we can. (Sounds like Mr. Obama!) > > Nuexo DM is based on Jackrabbit? > > On Wed, Mar 31, 2010 at 4:35 PM, Nirmal Sharma wrote: >> >> Hi, >> >> Can we develop Document Management System using Jackrabbit. Please provide >> related info, links, pointers. >> >> Regards, >> N > > > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
[jira] Commented: (JCR-322) Support node type modification and removal
[ https://issues.apache.org/jira/browse/JCR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840595#action_12840595 ] Paco Avila commented on JCR-322: Any work in the JSR 283 node type management API can deal with this ancient issue? > Support node type modification and removal > -- > > Key: JCR-322 > URL: https://issues.apache.org/jira/browse/JCR-322 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: nodetype >Affects Versions: 0.9, 1.0 >Reporter: Jukka Zitting > Attachments: nodetyperegistry.patch, OKMSystemSession.java > > > There is currently no way to modify or remove registered node types. The > existing reregister and unregister methods in NodeTypeRegistry throw "not > yet implemented" exceptions for anything else than trivial node type changes. > JSR 283 is working on an node type management API that we should ultimately > implement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1697) Simple Google style query
[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840135#action_12840135 ] Paco Avila edited comment on JCR-1697 at 3/2/10 12:02 PM: -- Sorry, I have created a new issue at JCR-2526, so we can move the discussion there. was (Author: monkiki): Sorry, I have created a new issue at JCR-2526. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1697) Simple Google style query
[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840135#action_12840135 ] Paco Avila commented on JCR-1697: - Sorry, I have created a new issue at JCR-2526. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-2526) Make o.a.j.commons.query.GQL modular
Make o.a.j.commons.query.GQL modular Key: JCR-2526 URL: https://issues.apache.org/jira/browse/JCR-2526 Project: Jackrabbit Content Repository Issue Type: Wish Components: jackrabbit-jcr-commons Affects Versions: 1.6.1 Reporter: Paco Avila Priority: Minor The GQL.execute() returns a RowIterator and would be nice to return a QueryResult, so I can make a result.getColumnNames() to get the returned column names. Or perhaps better, make public the method which translates the GQL query to XPath so I can pass it to the QueryManager and execute it. Previously discussed at JCR-1697. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1248) Helper Method to escape illegal XPath Search Term
[
https://issues.apache.org/jira/browse/JCR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840071#action_12840071
]
Paco Avila commented on JCR-1248:
-
I'm not sure if is a bug or a "feature". The query
String term = "pe[]pe";
String scapedTerm = Text.escapeIllegalXpathSearchChars(term).replaceAll("'",
"''")
String query = "/jcr:root//*[jcr:contains(okm:content,'"+escapedTerm+"')]"
should fail or the term "pe[]pe" should be escaped as "pe\[\]pe"?
> Helper Method to escape illegal XPath Search Term
> -
>
> Key: JCR-1248
> URL: https://issues.apache.org/jira/browse/JCR-1248
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr-commons
>Reporter: Claus Köll
>Assignee: Claus Köll
>Priority: Minor
> Fix For: 1.5.0
>
> Attachments: patch.txt
>
>
> If you try to perform a search like this
> //element(*, nt:base)[jcr:contains(., 'test!')]
> you get this exception
> javax.jcr.RepositoryException: Exception building query:
> org.apache.jackrabbit.core.query.lucene.fulltext.ParseException: Encountered
> "" at line 1, column 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1248) Helper Method to escape illegal XPath Search Term
[
https://issues.apache.org/jira/browse/JCR-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840068#action_12840068
]
Paco Avila commented on JCR-1248:
-
By the way, this sample code at
http://wiki.apache.org/jackrabbit/EncodingAndEscaping is recursive:
String q =
"/jcr:root/foo/element(*, foo)" +
"[jcr:contains(@title, '" +
Text.escapeIllegalXpathSearchChars(q).replaceAll("'", "''") + "')]" +
"[...@itemid = '" + itemID.replaceAll("'", "''") + "']";
> Helper Method to escape illegal XPath Search Term
> -
>
> Key: JCR-1248
> URL: https://issues.apache.org/jira/browse/JCR-1248
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr-commons
>Reporter: Claus Köll
>Assignee: Claus Köll
>Priority: Minor
> Fix For: 1.5.0
>
> Attachments: patch.txt
>
>
> If you try to perform a search like this
> //element(*, nt:base)[jcr:contains(., 'test!')]
> you get this exception
> javax.jcr.RepositoryException: Exception building query:
> org.apache.jackrabbit.core.query.lucene.fulltext.ParseException: Encountered
> "" at line 1, column 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1697) Simple Google style query
[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840064#action_12840064 ] Paco Avila commented on JCR-1697: - GQL is already in jcr-commons, so the purity is broken. Anyway, my principal problem is that I can paginate the result of GQL, because the optimized method seems to be: ((QueryImpl) query).setLimit(limit); ((QueryImpl) query).setOffset(offset); and it return a RowIterator. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1697) Simple Google style query
[ 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 internally making possible to run it as: queryManager.createQuery(statement, type); Where "type" could be "gql" in this case, and the statement a GQL query. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1697) Simple Google style query
[ 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 to return a QueryResult, so I can make a result.getColumnNames() to get the returned column names. Or perhaps better, make public the method which translates the GQL query to XPath so I can pass it to the QueryManager and execute it. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1248) Helper Method to escape illegal XPath Search Term
[ 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 like this will fail: //element(*, nt:base)[jcr:contains(., 'test \ done')] Specification JSR-170 at point 6.6.5.2 says that literal instances like single quote ( ' ), double quote ( " ) and hyphen ( - ) must be escaped with a backslash ( \ ), and backslash itself should be escaped as a double backslash ( \\ ). Also, I have noted that some chars like [ and ] need to be escaped also. was (Author: monkiki): A query like this will fail: //element(*, nt:base)[jcr:contains(., 'test[')] Specification JSR-170 at point 6.6.5.2 says that literal instances like single quote ( ' ), double quote ( " ) and hyphen ( - ) must be escaped with a backslash ( \ ), and backslash itself should be escaped as a double backslash ( \\ ). Also, I have noted that some chars like [ and ] need to be escaped also. > Helper Method to escape illegal XPath Search Term > - > > Key: JCR-1248 > URL: https://issues.apache.org/jira/browse/JCR-1248 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Claus Köll >Assignee: Claus Köll >Priority: Minor > Fix For: 1.5.0 > > Attachments: patch.txt > > > If you try to perform a search like this > //element(*, nt:base)[jcr:contains(., 'test!')] > you get this exception > javax.jcr.RepositoryException: Exception building query: > org.apache.jackrabbit.core.query.lucene.fulltext.ParseException: Encountered > "" at line 1, column 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1248) Helper Method to escape illegal XPath Search Term
[ 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:contains(., 'test[')] Specification JSR-170 at point 6.6.5.2 says that literal instances like single quote ( ' ), double quote ( " ) and hyphen ( - ) must be escaped with a backslash ( \ ), and backslash itself should be escaped as a double backslash ( \\ ). Also, I have noted that some chars like [ and ] need to be escaped also. > Helper Method to escape illegal XPath Search Term > - > > Key: JCR-1248 > URL: https://issues.apache.org/jira/browse/JCR-1248 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Claus Köll >Assignee: Claus Köll >Priority: Minor > Fix For: 1.5.0 > > Attachments: patch.txt > > > If you try to perform a search like this > //element(*, nt:base)[jcr:contains(., 'test!')] > you get this exception > javax.jcr.RepositoryException: Exception building query: > org.apache.jackrabbit.core.query.lucene.fulltext.ParseException: Encountered > "" at line 1, column 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Jackrabbit 1.6.1
+1 On Tue, Jan 19, 2010 at 9:59 AM, Sébastien Launay wrote: > Hi, > > [X] +1 Release this package as Apache Jackrabbit 1.6.1 > > - checksums [OK] > - signature [OK] > - license, notice, header and readme files [OK] > - maven build [OK] with Ubuntu Jaunty / Sun Java 1.6.0_14-b08 > > I do not test the maven artifacts just the sources package, the war > and the standalone jar. > > -- > Sébastien Launay > -- OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: detect a failed text extraction?
On Wed, Nov 25, 2009 at 2:26 PM, Jukka Zitting wrote: > Hi, > > On Tue, Nov 24, 2009 at 8:53 PM, Paco Avila wrote: >> There is any way to detect a failed text extraction ? I know, I can >> see the log but the failure it not associated to a file or path. >> [...] >> I have posted this question in the user list, but I think it is >> interesting talking about how it can be achieved. > > Could we solve this by improving the level of logging in the indexer? > > Alternatively, if you don't have easy access to the log files, we > could possibly inject some special unique term to the index as a > marker of failed text extraction. That way you could query for all > nodes for which text extraction failed. Increasing the log level can be a goog approach: the objective is link a failed text extraction with a node path. This way, I can see if the submitted document has failed in the text extraction process. The other approach (injecting a special term) also is very cute because I can get a list of failed indexed document from a XPath query. Both solutions can be combined to improve the jackrabbit experience: the XPath query give a list of unindexed document and the log can hep to know what failed in the text extraction. > Finally, as a debugging tool we could add a feature to the Jackrabbit > webapp that allows you to download the extracted text content of a > binary instead of the binary itself. We'd simply run a new text > extraction pass on the stored binary and return the extracted text or > any encountered errors to he client. This also can be interesting. > > BR, > > Jukka Zitting > -- Paco Avila OpenKM http://www.openkm.com http://www.guia-ubuntu.org
detect a failed text extraction?
There is any way to detect a failed text extraction ? I know, I can see the log but the failure it not associated to a file or path. Some times when I upload a document (word, pdf, etc.) to my DMS build on Jackrabbit, it is not indexed. Office documents seems to be specially problematic due to its propietary format. And the problem is that I don't know which document had problems it their text extraction, specially if use extractorPoolSize > 1. I have posted this question in the user list, but I think it is interesting talking about how it can be achieved. -- Paco Avila OpenKM http://www.openkm.com http://www.guia-ubuntu.org
Re: Jackrabbit Vs Alfresco
Jackrabbit is the reference implementation of JCR-170. It's a framework not an CMS. Alfresco has its own implementation of JCR-170. You can compare Alfresco with OpenKM (anr document managemen system built-on jackrabbit. On Wed, Oct 7, 2009 at 10:00 AM, Dhananjay Mahajan < dmaha...@techmahindra.com> wrote: > Hi All, > > > > Can you please send across the detail feature list of Jackrabbit Vs > Alfresco ? > > > > As both are open source , this comparison will help to decide the CMS. > > > > Regards > > Dhananjay Mahajan > > > > > Disclaimer: > > This message and the information contained herein is proprietary and > confidential and subject to the Tech Mahindra policy statement, you may > review the policy at http://www.techmahindra.com/Disclaimer.htmlexternally and > http://tim.techmahindra.com/Disclaimer.html internally within Tech > Mahindra. > > > ==== > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Re: [VOTE] Release jackrabbit-core 1.4.11
+1 On sep 18, 2009 6:10 p.m., "Jukka Zitting" wrote: Hi, I have posted a candidate for the jackrabbit-core 1.4.11 release at: http://people.apache.org/~jukka/jackrabbit/core-1.4.11/ The staged Maven repository is at: https://repository.apache.org/content/repositories/jackrabbit-034/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details on release contents and latest changes. The release candidate is a jar archive of the sources in http://svn.apache.org/repos/asf/jackrabbit/tags/jackrabbit-core-1.4.11. The SHA1 checksum of the release package is 306460fc3be6a061467bbf1c8d5ee3d0d0f8f82b. Please vote on releasing this package as jackrabbit-core 1.4.11. The vote is open for the next 72 hours and passes if a majority of at least three +1 votes are cast. The vote is open for everyone but only votes from Jackrabbit PMC members are binding. [ ] +1 Release this package as jackrabbit-core 1.4.11 [ ] -1 Do not release this package because... Here's my +1. BR, Jukka Zitting Release Notes -- Apache Jackrabbit Core -- Version 1.4.11 Introduction This is the 1.4.11 patch release of the jackrabbit-core component of Apache Jackrabbit, a fully conforming implementation of the Content Repository for Java Technology API (JCR). This release is targeted to users who are not yet ready to upgrade to the more recent Jackrabbit releases, but who still need the XPath formatting fix from issue JCR-2052. See the Apache Jackrabbit website at http://jackrabbit.apache.org/ for more information. Changes in this release --- All the changes in this release are listed below. The issue identifier and title is listed for each change and known issue. You can look up individual issues for more details in the Jackrabbit issue tracker at http://issues.apache.org/jira/browse/JCR Bug fixes [JCR-2052] XPath QueryFormat may produce malformed XPath statement Release Contents Like the previous jackrabbit-core 1.4.x releases this patch release only contains the jackrabbit-core component. The component is distributed both as a source archive and a pre-compiled binary. * Source archive (jackrabbit-core-1.4.11-src.jar) The source archive contains the full source code of this release in a "jackrabbit-core-1.4.11" directory. Use the following commands (or the equivalent in your environment) to build the component with Maven 2 and Java 1.4 or higher: $ jar xf jackrabbit-core-1.4.11-src.jar $ cd jackrabbit-core-1.4.11 $ mvn install * Pre-compiled binary (jackrabbit-core-1.4.11.jar) Core of the Apache Jackrabbit content repository implementation. See the included README.txt file for more information. Each release file is accompanied by SHA1 and MD5 checksums and a PGP signature. The public key used for the signatures can be found in the KEYS file.
Re: [VOTE] Release Apache Jackrabbit 1.6.0
Fabrizio GiustinaOleg Alexeyev Ard Schrijvers Felix MeschbergerPaco Avila Arthur MeyerGreg Klebus Roman Puchkovskiy Attila Király Jacco van Weert Ryan Vanderwerf Bart van der Schans James Abley Sandrine Raffalli Boni GopalanJason GritmanSavvas Triantafyllou Brian Whipple Jukka ZittingSébastien Launay Cédric Damioli Julian Reschke Stefan Guggisberg Charles BrookingJulian Sedding Stephane Landelle Christian Ken Yue Thomas Fromm Christophe Lombart Marcel Reutegger Thomas Mueller Claus Köll Marius Ropotica Tobias Bocanegra Dan Diephouse Martijn Hendriks Torsten Weck Dave BrosiusMicah Whitacre Tyson Norris Dirk Feufel Michael DürigYoav Landman Thank you to everyone involved! About Apache Jackrabbit --- Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more. Typical applications that use content repositories include content management, document management, and records management systems. For more information, visit http://jackrabbit.apache.org/ About The Apache Software Foundation Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 100 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property framework limits the legal exposure of its 2,500+ contributors. For more information, visit http://www.apache.org/
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: CheckinCalendarTest.java The missing test class > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila >Assignee: Jukka Zitting > Fix For: 1.6.0 > > Attachments: CheckinCalendarTest.java, Jackrabbit_modifications.pdf, > JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.patch, JCR-1972_1.x.patch, > JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738544#action_12738544 ] Paco Avila commented on JCR-1972: - Sorry for the missing test class. I did no review of the generated patch and thought it was included. I'm on holiday but i will try to get a decent Internet connection to attach the missing class. > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila >Assignee: Jukka Zitting > Fix For: 1.6.0 > > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch, JCR-1972_1.x.patch, JCR-1972_1.x.patch, JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: JCR-1972_1.x.patch Improvements by recommendation of Jukka > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila >Assignee: Jukka Zitting > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch, JCR-1972_1.x.patch, JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731866#action_12731866 ] Paco Avila edited comment on JCR-1972 at 7/16/09 2:06 AM: -- Updated patch -> Check for existing UUID. I have to duplicate some methods to add a new parameter with the UUID. was (Author: monkiki): Updated patch -> Check for existing UUID > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch, JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731866#action_12731866 ] Paco Avila edited comment on JCR-1972 at 7/16/09 2:05 AM: -- Updated patch -> Check for existing UUID was (Author: monkiki): Check for existing UUID > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch, JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: JCR-1972_1.x.patch Check for existing UUID > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch, JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Using Eclipse for Jackrabbit development (Was: Is JCR-1972 going to be included?)
So using m2eclipse is the preferred way to deal with jackrabbit (subversion) and eclipse. If I use m2eclipse is necessary to run "mvn eclipse:eclipse" ? I'm not sure of this. Actually I'm not using the eclipse plugin so working in the old-fashioned way, but it is working fine (more or less) On Mon, Jul 13, 2009 at 2:28 PM, Guo Du wrote: > The article should still works, because it follow Michael's > instruction. Just noticed it's quite old: August 15, 2007. > > I did a try for m2eclipse recently and it give much better experience > than it's early version. It has a GUI to manage your pom (You don't > need to check the pom model manual any more) and update eclipse > dependencies automatically. Import and run goals inside IDE also give > better productivity. > > -- Guo > > On Mon, Jul 13, 2009 at 12:53 PM, Paco Avila wrote: > > > > This article is very clear about it: > > > > http://www.jroller.com/cdaniluk/entry/setting_up_an_eclipse_multi > > > > I will try this instructions. > > > > On Mon, Jul 13, 2009 at 1:09 PM, Michael Dürig > wrote: > >>> I've some problems developing with jackrabbit in Eclipse. Where can I > >>> find > >>> some info about this? > >> > >> There are many ways to do this, but I'm pretty happy with the > >> m2eclipse plugin from http://m2eclipse.sonatype.org/. > >> > >> The plugin installs cleanly from the update site at > >> http://m2eclipse.sonatype.org/update/, and after that I can use File > > >> Import... > Maven Projects and point the dialog to the root of my > >> checkout. The importer will correctly find and set up all the > >> components as separate projects in Eclipse. > > > > I use a similar approach but without the m2eclipse plugin. Rather I use > > Maven from the command line: > > > > mvn clean install > > mvn eclipse:eclipse > > > > and then import the generated eclipse project files with Eclipse. > > > > This approach works generally quite well. > > > > Michael > > > > > > > > -- > Kind regards, > > Du, Guo > __ > Phone : +353-86-176 6186 > Email : onl...@duguo.com > __ > http://duguo.com - Career Life Balance > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
[jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730372#action_12730372 ] Paco Avila commented on JCR-1972: - I've updated the patch and also added two JUnit test (CheckinCalendarTest and added a new method at NodeImplTest). In addNode(..., UUID) I can test if the node has the MIX_REFERENCEABLE mixing but I'm not sure if this good because the mixin can be added after the node creation. This check is commented in the patch. > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Comment: was deleted (was: In 1.x branch, the class org.apache.jackrabbit.core.NodeImpl.java is this: public synchronized NodeImpl addNode(Name nodeName, Name nodeTypeName, UUID uuid) So, it already accept an UUID parameter for new node creation.) > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: JCR-1972_1.x.patch Updated patch for the 1.x branch > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, > JCR-1972_1.x.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730304#action_12730304 ] Paco Avila commented on JCR-1972: - In 1.x branch, the class org.apache.jackrabbit.core.NodeImpl.java is this: public synchronized NodeImpl addNode(Name nodeName, Name nodeTypeName, UUID uuid) So, it already accept an UUID parameter for new node creation. > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Is JCR-1972 going to be included?
This article is very clear about it: http://www.jroller.com/cdaniluk/entry/setting_up_an_eclipse_multi I will try this instructions. On Mon, Jul 13, 2009 at 1:03 PM, Paco Avila wrote: > I've some problems developing with jackrabbit in Eclipse. Where can I find > some info about this? The "problem" is due maven2 modules and Eclipse > project mapping. I have spend some time searching in Google with little > luck. > > > On Fri, Jul 10, 2009 at 4:23 PM, Jukka Zitting wrote: > >> Hi, >> >> On Fri, Jul 10, 2009 at 4:10 PM, Paco Avila wrote: >> > I will try to send the patch in a couple of days. >> >> Thanks! There's no pressing need for the 1.6 release, so I don't mind >> waiting a bit longer before cutting the release candidate. >> >> BR, >> >> Jukka Zitting >> > > > > -- > Paco Avila > GIT Consultors > tel: +34 971 498310 > fax: +34 971496189 > e-mail: pav...@git.es > http://www.git.es > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Re: Is JCR-1972 going to be included?
I've some problems developing with jackrabbit in Eclipse. Where can I find some info about this? The "problem" is due maven2 modules and Eclipse project mapping. I have spend some time searching in Google with little luck. On Fri, Jul 10, 2009 at 4:23 PM, Jukka Zitting wrote: > Hi, > > On Fri, Jul 10, 2009 at 4:10 PM, Paco Avila wrote: > > I will try to send the patch in a couple of days. > > Thanks! There's no pressing need for the 1.6 release, so I don't mind > waiting a bit longer before cutting the release candidate. > > BR, > > Jukka Zitting > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Re: Is JCR-1972 going to be included?
I will try to send the patch in a couple of days. El 10 de jul de 2009, 4:03 p.m., "Jukka Zitting" escribió: Hi, On Fri, Jul 10, 2009 at 3:57 PM, Paco Avila wrote: > When is planned the 1.6 release... I was thinking of cutting the release candidate now over the weekend. :-) That would make the release happen next week unless any issues come up before that. BR, Jukka Zitting
Re: Is JCR-1972 going to be included?
When is planned the 1.6 release? El 10 de jul de 2009, 2:45 p.m., "Jukka Zitting" escribió: Hi, On Fri, Jul 10, 2009 at 2:27 PM, Paco Avila wrote: > I see a subversion branch c... Yes, that's what we'll be using for the 1.6 release and possibly 1.7 after that (only if needed). BR, Jukka Zitting
Re: Is JCR-1972 going to be included?
I see a subversion branch called "1.x". Is this what I have to download and test the patch? On Fri, Jul 10, 2009 at 2:01 PM, Paco Avila wrote: > Ok, I will download 1.6.0 and will try the patch. Once included the patch I > can contribute with an migration utilty (perhaps to the sandbox) > > > On Fri, Jul 10, 2009 at 1:37 PM, Jukka Zitting wrote: > >> Hi, >> >> On Fri, Jul 10, 2009 at 12:19 PM, Paco Avila wrote: >> > I wonder if the patch JCR-1972 is going to be included in a near >> release, >> > because I have to update it to match a recent jackrabbit-core version. >> >> I like the idea so I think it would be good to have it included, >> perhaps already in 1.6.0. Can you check that the patch is fine with >> the 1.x branch? >> >> There may be some minor adjustments that we need to do before applying >> the patch though, I'll comment more in the issue. >> >> BR, >> >> Jukka Zitting >> > > > > -- > Paco Avila > GIT Consultors > tel: +34 971 498310 > fax: +34 971496189 > e-mail: pav...@git.es > http://www.git.es > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Re: Is JCR-1972 going to be included?
Ok, I will download 1.6.0 and will try the patch. Once included the patch I can contribute with an migration utilty (perhaps to the sandbox) On Fri, Jul 10, 2009 at 1:37 PM, Jukka Zitting wrote: > Hi, > > On Fri, Jul 10, 2009 at 12:19 PM, Paco Avila wrote: > > I wonder if the patch JCR-1972 is going to be included in a near release, > > because I have to update it to match a recent jackrabbit-core version. > > I like the idea so I think it would be good to have it included, > perhaps already in 1.6.0. Can you check that the patch is fine with > the 1.x branch? > > There may be some minor adjustments that we need to do before applying > the patch though, I'll comment more in the issue. > > BR, > > Jukka Zitting > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Is JCR-1972 going to be included?
I wonder if the patch JCR-1972 is going to be included in a near release, because I have to update it to match a recent jackrabbit-core version. -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
[jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729069#action_12729069 ] Paco Avila commented on JCR-1972: - As I wrote some time ago, these modifications make two enhacements in the jackrabbit-core functionality: - Enable UUID parameter in addNode: this allow to preserve the unique node identifier across a repository migration. If you use references this change is fundamental. - Enable Calendar parameter in checkin: this change can be used to preserve checking date in document version history in a possible migration. This migration can be of two types: - Change the repository backend: you use the default Derby database, but you want to swith to MySQL, for example. Actually this is not possible in a easy way. - Change the repository node definitions: jackrabbit actually can't deal with these changes depending on their complexity. You have to write a program to make this migration. >From my point of view, this patch introduces very neccessary funtionality into >Jackrabbit. If you want to include these modifications in a near release, I >can try to send a new patch that works with an specific jackrabbit-core >version. > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671842#action_12671842 ] monkiki edited comment on JCR-1972 at 2/9/09 5:10 AM: - Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1.4.6 and i'm not sure if it works for more recent versions. was (Author: monkiki): Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1.4.6 > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 >Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: JCR-1972.patch Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1.4.6 > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: Jackrabbit_modifications.pdf This PDF shows the modifications needed in the jackrabbit core to preserve node UUID and document version history date in repository migrations. > Preserving UUID and document version history on repository migration > > > Key: JCR-1972 > URL: https://issues.apache.org/jira/browse/JCR-1972 > Project: Jackrabbit Content Repository > Issue Type: Wish > Components: jackrabbit-core >Affects Versions: core 1.4.8 > Reporter: Paco Avila > Attachments: Jackrabbit_modifications.pdf > > > I have been working I an migration utility for OpenKM and I performed some > changes in jackrabit-core to enable version import, preserving > the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to > preserve UUID in the migration process. > This migration process is needed because there are changes in repository node > definition, and Jackrabbit can't deal with this actually. > I've attache a PDF with the changes needed in Jackrabbit-core. It works and > there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1972) Preserving UUID and document version history on repository migration
Preserving UUID and document version history on repository migration Key: JCR-1972 URL: https://issues.apache.org/jira/browse/JCR-1972 Project: Jackrabbit Content Repository Issue Type: Wish Components: jackrabbit-core Affects Versions: core 1.4.8 Reporter: Paco Avila I have been working I an migration utility for OpenKM and I performed some changes in jackrabit-core to enable version import, preserving the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to preserve UUID in the migration process. This migration process is needed because there are changes in repository node definition, and Jackrabbit can't deal with this actually. I've attache a PDF with the changes needed in Jackrabbit-core. It works and there was no problems with the migrated repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: locking question
On Thu, Jan 15, 2009 at 8:48 AM, KÖLL Claus wrote: > hi @ all > > i dont know if it is a bug or "works as designed" but if i try ... > > Node n1 = testRootNode.addNode(nodeName1); > n1.addMixin(mixLockable); > n1.addMixin(mixReferenceable); > testRootNode.save(); > > Lock lock = n1.lock(true, false); /** No session scoped lock ! > String lockToken = lock.getLockToken(); > String path = n1.getPath(); > > //superuser.logout(); <- only if i logout the session that creates the lock i > get no exception ! > > Session otherSuperuser = helper.getSuperuserSession(); > otherSuperuser.addLockToken(lockToken); > Node n2 = (Node) otherSuperuser.getItem(path); > n2.unlock(); > > i get a LockException "Node not locked by session" > as written above ... only if i logout the session that creates the lock i get > no exception > > i didnt found anything about that in the spec ... > WDOT ? > > greets > claus > The lock token can't be owned by two sessions at the same time. -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: pav...@git.es http://www.git.es
Re: Comparing by time
Use "org.apache.jackrabbit.util.ISO8601" for date format. On Thu, Nov 13, 2008 at 2:09 PM, Jukka Zitting <[EMAIL PROTECTED]>wrote: > Hi, > > On Thu, Nov 13, 2008 at 1:22 AM, pkrishna <[EMAIL PROTECTED]> > wrote: > > I am trying to do a search based on Modified time. What I am observing is > the > > time format in the node is different from when I am using a > > SimpleDateFormat; For example, in the node the lastModified time is saved > as > > 2008-11-12T16:46:57.089-07:00. I used SimpleDateFormat using the pattern > > -MM-dd'T'HH:mm:ss.SSSZ which seems to be the closest to the format of > > the time in the node. I observed for the same date, the call > > SimpleDateFormat.format produces a string which ends with -700 which is > > slightly different from -07:00. So my question is how I incorporate into > a > > query that does an exact match on the date. Is this even possible? > > The easiest way to format dates using the exact format specified in > JSR-170 is to use the following code: > >Calendar date = ...; >session.getValueFactory().getValue(date).getString(); > > Similarly, you can parse JSR-170 date values like this: > >String date = ...; >session.getValueFactory().getValue(date).getDate(); > > BR, > > Jukka Zitting > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: [EMAIL PROTECTED] http://www.git.es
[jira] Commented: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646585#action_12646585 ] Paco Avila commented on JCR-1521: - I'm interested in correct this behavior, but not sure how can I do it. There is more users interested in this issue and want to meet a good solution? I think that a good way to avoid re-index the data is add a new property which contains a checksum for jcr:data property. > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Improvement > Components: indexing, jackrabbit-core >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New Jackrabbit committer
congrats! On 10/17/08, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > Please welcome Claus Köll as a new committer and PMC member of the > Apache Jackrabbit project! > > Claus has been a long term contributor with an excellent record of > high quality patches and other contributions, and so the Jackrabbit > PMC recently decided to offer him committership. All the related > administrative work has now been taken care of, and I am happy to > announce that Claus is now a Jackrabbit committer. > > Welcome to the team, Claus! > > BR, > > > Jukka Zitting > -- Paco Avila GIT Consultors tel: +34 971 498310 fax: +34 971496189 e-mail: [EMAIL PROTECTED] http://www.git.es
[jira] Created: (JCR-1780) Wiki reference a missing CND resource
Wiki reference a missing CND resource - Key: JCR-1780 URL: https://issues.apache.org/jira/browse/JCR-1780 Project: Jackrabbit Issue Type: Bug Reporter: Paco Avila Wiki page "http://wiki.apache.org/jackrabbit/nt%3aexample"; references a missing resource: "http://jackrabbit.apache.org/doc/nodetype/cnd.html"; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1779) recursion problem in indexing configuration
[ https://issues.apache.org/jira/browse/JCR-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636051#action_12636051 ] monkiki edited comment on JCR-1779 at 10/1/08 7:27 AM: -- This is only a WARNing and the repository is created correctly, and you can register the namespaces. The next time you start the repository all is ok and no WARNing is shown in the log. But is ugly for the poor user :) was (Author: monkiki): This is only a WARNing and the repository is created correctly, and you can register the namespaces. The next time you start the repository all is ok and no WARNing is shown in the log. > recursion problem in indexing configuration > --- > > Key: JCR-1779 > URL: https://issues.apache.org/jira/browse/JCR-1779 > Project: Jackrabbit > Issue Type: Bug > Environment: Hardy Hero - Ubuntu Linux > Reporter: Paco Avila > > I have an indexing configurator file with wich reference my own namespace. > The problem is when I want to create a new repository: an exceptin is thrown > (IllegalNameException) because the namespace still is not registerd in the > repository. And how can I register a namespace if the repository is not > actually created? > It seems to be a sort of recursion problem to me :( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1779) recursion problem in indexing configuration
[ https://issues.apache.org/jira/browse/JCR-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636051#action_12636051 ] monkiki edited comment on JCR-1779 at 10/1/08 7:26 AM: -- This is only a WARNing and the repository is created correctly, and you can register the namespaces. The next time you start the repository all is ok and no WARNing is shown in the log. was (Author: monkiki): This is a WARNing and can be ignored because the next time you start the repository, is ok. > recursion problem in indexing configuration > --- > > Key: JCR-1779 > URL: https://issues.apache.org/jira/browse/JCR-1779 > Project: Jackrabbit > Issue Type: Bug > Environment: Hardy Hero - Ubuntu Linux > Reporter: Paco Avila > > I have an indexing configurator file with wich reference my own namespace. > The problem is when I want to create a new repository: an exceptin is thrown > (IllegalNameException) because the namespace still is not registerd in the > repository. And how can I register a namespace if the repository is not > actually created? > It seems to be a sort of recursion problem to me :( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1779) recursion problem in indexing configuration
[ https://issues.apache.org/jira/browse/JCR-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636051#action_12636051 ] Paco Avila commented on JCR-1779: - This is a WARNing and can be ignored because the next time you start the repository, is ok. > recursion problem in indexing configuration > --- > > Key: JCR-1779 > URL: https://issues.apache.org/jira/browse/JCR-1779 > Project: Jackrabbit > Issue Type: Bug > Environment: Hardy Hero - Ubuntu Linux > Reporter: Paco Avila > > I have an indexing configurator file with wich reference my own namespace. > The problem is when I want to create a new repository: an exceptin is thrown > (IllegalNameException) because the namespace still is not registerd in the > repository. And how can I register a namespace if the repository is not > actually created? > It seems to be a sort of recursion problem to me :( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1779) recursion problem in indexing configuration
recursion problem in indexing configuration --- Key: JCR-1779 URL: https://issues.apache.org/jira/browse/JCR-1779 Project: Jackrabbit Issue Type: Bug Environment: Hardy Hero - Ubuntu Linux Reporter: Paco Avila I have an indexing configurator file with wich reference my own namespace. The problem is when I want to create a new repository: an exceptin is thrown (IllegalNameException) because the namespace still is not registerd in the repository. And how can I register a namespace if the repository is not actually created? It seems to be a sort of recursion problem to me :( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Which method use to encode invalid chars in node name?
Sorry, a mistake in my To field :( On Tue, Jul 29, 2008 at 1:46 PM, Angela Schreiber <[EMAIL PROTECTED]> wrote: > Paco Avila wrote: > >> ISO9075.encode(name), Text.escapeIllegalJcrChars(name) or >> Text.escape(name) >> ? >> > > see my previous mail to the user list. > > btw, there is no need to send a mail to both user and > dev list, nor to post things twice. > > thanks > angela > > >
Which method use to encode invalid chars in node name?
ISO9075.encode(name), Text.escapeIllegalJcrChars(name) or Text.escape(name) ?
[jira] Updated: (JCR-1620) Make the Analyzer configurable per node (or subtree)
[ https://issues.apache.org/jira/browse/JCR-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1620: Description: Would be nice that Jackrabbit could index documents in several languages and use an specific Lucene Analizer for each one to get optimal quesy results. (was: Would be nice that Jackrabbit could index documents in several languages and use an specific Lucene Analizer for echar one to get optimal quesy results.) > Make the Analyzer configurable per node (or subtree) > > > Key: JCR-1620 > URL: https://issues.apache.org/jira/browse/JCR-1620 > Project: Jackrabbit > Issue Type: Improvement > Components: indexing > Reporter: Paco Avila > > Would be nice that Jackrabbit could index documents in several languages and > use an specific Lucene Analizer for each one to get optimal quesy results. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1620) Make the Analyzer configurable per node (or subtree)
Make the Analyzer configurable per node (or subtree) Key: JCR-1620 URL: https://issues.apache.org/jira/browse/JCR-1620 Project: Jackrabbit Issue Type: Improvement Components: indexing Reporter: Paco Avila Would be nice that Jackrabbit could index documents in several languages and use an specific Lucene Analizer for echar one to get optimal quesy results. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New Jackrabbit committer
El mar, 22-04-2008 a las 03:44 +0300, Jukka Zitting escribió: > Hi, > > Please welcome Esteban Franqueiro as a new committer and PMC member of > the Apache Jackrabbit project. The Jackrabbit PMC recently decided to > offer Esteban committership based on his contributions. I'm happy to > announce that he accepted the offer and that all the related > administrative work has now been taken care of. > > Welcome to the team, Esteban! Congratulations! :) -- Paco Avila <[EMAIL PROTECTED]> GIT Consultors
[jira] Issue Comment Edited: (JCR-1455) Content browser/editor
[ https://issues.apache.org/jira/browse/JCR-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590891#action_12590891 ] monkiki edited comment on JCR-1455 at 4/21/08 4:21 AM: -- I've been testing "CRX Content Explorer" and looks great :) But now I have a question because I've seen the Access-Control Editor : how do you implement the ACL? There is no default ACL managemente in Jackrabbit was (Author: monkiki): I've been testing "CRX Content Explorer" and looks great :) But now I have a question because I've seen the Access-Control Editor : how do you implement the ACL? There is no default ACL managemente in Jackrabbit > Content browser/editor > -- > > Key: JCR-1455 > URL: https://issues.apache.org/jira/browse/JCR-1455 > Project: Jackrabbit > Issue Type: New Feature > Components: jackrabbit-webapp >Reporter: Jukka Zitting > Fix For: 1.5 > > > The Jackrabbit webapp should come with a web-based content browser/editor > tool that can be used to manage the content in the repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1455) Content browser/editor
[ https://issues.apache.org/jira/browse/JCR-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590891#action_12590891 ] Paco Avila commented on JCR-1455: - I've been testing "CRX Content Explorer" and looks great :) But now I have a question because I've seen the Access-Control Editor : how do you implement the ACL? There is no default ACL managemente in Jackrabbit > Content browser/editor > -- > > Key: JCR-1455 > URL: https://issues.apache.org/jira/browse/JCR-1455 > Project: Jackrabbit > Issue Type: New Feature > Components: jackrabbit-webapp >Reporter: Jukka Zitting > Fix For: 1.5 > > > The Jackrabbit webapp should come with a web-based content browser/editor > tool that can be used to manage the content in the repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Content explorer (Re: Jackrabbit 1.5 release plan)
El lun, 21-04-2008 a las 00:22 +0200, Greg Klebus escribió: > We at Day decided to donate the CRX Content Explorer, part of our > Content Repository Extreme product, to the community / Jackrabbit. For > those, who'd like to have a look at the current CRX content explorer, > please see the live CRX demo [2] and click on 'Content Explorer' link > to play with it. I've been testing "CRX Content Explorer" and looks great :) But now I have a question because I've seen the Access-Control Editor : how do you implement the ACL? There is no default ACL managemente in Jackrabbit. Cheers! -- Paco Avila <[EMAIL PROTECTED]> GIT Consultors
[jira] Commented: (JCR-1521) Text Extractors are executed twice
[
https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589107#action_12589107
]
Paco Avila commented on JCR-1521:
-
Ja, ja... good but it is very annoying force text extraction on checkout. The
checkout opperation does no modify any "interesting" node property which
justify node content reindexing.
A, from my point of view, good way to avoid reindex binary can be add a
checksum property which can be used to check if the binary content is modified.
Or put a isModified property with is set to true when user do
ContenNode.setProperty("jcr:data", xxx) .
> Text Extractors are executed twice
> --
>
> Key: JCR-1521
> URL: https://issues.apache.org/jira/browse/JCR-1521
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-text-extractors
>Affects Versions: 1.4
> Environment: JDK 1.5 Ubuntu Gutsy
>Reporter: Paco Avila
> Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java,
> ExifTextExtractor.java, StackTrace.txt
>
>
> I'have created a test text extractor and the method extractText() is invoked
> twice. It it really neccesaty or it's a bug?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila reopened JCR-1521: - The text extractor is executed after Node.save() and after Node.checkin() > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: DummyTextExtractor.java TextExtractor is executer after Node.save(), Node.checking() and Node.checkout() > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: (was: DummyTextExtractor.java) > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: DummyTextExtractor.java Sample code to reproduce issue > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: DummyMyTextExtractor.java Simple dummy text extractor > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: DummyMyTextExtractor.java, DummyTextExtractor.java, > ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1533) Update POI dependency to 3.0.2-FINAL
[ https://issues.apache.org/jira/browse/JCR-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587950#action_12587950 ] Paco Avila commented on JCR-1533: - I tested POI 3.0.2 and go back to 3.0.1 because fails to extract on some Excel files. > Update POI dependency to 3.0.2-FINAL > > > Key: JCR-1533 > URL: https://issues.apache.org/jira/browse/JCR-1533 > Project: Jackrabbit > Issue Type: Improvement > Components: jackrabbit-text-extractors >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5 > > > 3.0.2-FINAL is the most recent POI release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587888#action_12587888 ] monkiki edited comment on JCR-1521 at 4/11/08 1:53 AM: -- I can confirm that Upload and document creation is executen only one time. And ExifTextExtractor is executed twices because of log info messages. If the upload if executed twice and ItemAlreadyExistsException should be thrown and it is working fine. was (Author: monkiki): I can confirm that Upload and document creation is executen only one time. And ExifTextExtractor is executed twices because of log info messages. > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587888#action_12587888 ] Paco Avila commented on JCR-1521: - I can confirm that Upload and document creation is executen only one time. And ExifTextExtractor is executed twices because of log info messages. > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: StackTrace.txt This is the stackrtrace generated. > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java, StackTrace.txt > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587538#action_12587538 ] Paco Avila commented on JCR-1521: - No, this is done through jcr api. > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587226#action_12587226 ] Paco Avila commented on JCR-1521: - I have uploaded my ExitTextExtractor. This extractor is executed twice each time I put a jpg file into the repository. Used with * jackrabbit-api-1.4.jar * jackrabbit-core-1.4.2.jar * jackrabbit-jcr2spi-1.4.jar * jackrabbit-jcr-commons-1.4.2.jar * jackrabbit-spi-1.4.jar * jackrabbit-spi-commons-1.4.jar * jackrabbit-text-extractors-1.4.jar > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1521) Text Extractors are executed twice
[ https://issues.apache.org/jira/browse/JCR-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1521: Attachment: ExifTextExtractor.java This implements an (initial) text extractor for EXIF info stored in JPEG files. Need a jar from http://www.drewnoakes.com/code/exif/index.html > Text Extractors are executed twice > -- > > Key: JCR-1521 > URL: https://issues.apache.org/jira/browse/JCR-1521 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-text-extractors >Affects Versions: 1.4 > Environment: JDK 1.5 Ubuntu Gutsy >Reporter: Paco Avila > Attachments: ExifTextExtractor.java > > > I'have created a test text extractor and the method extractText() is invoked > twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1521) Text Extractors are executed twice
Text Extractors are executed twice -- Key: JCR-1521 URL: https://issues.apache.org/jira/browse/JCR-1521 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-text-extractors Affects Versions: 1.4 Environment: JDK 1.5 Ubuntu Gutsy Reporter: Paco Avila I'have created a test text extractor and the method extractText() is invoked twice. It it really neccesaty or it's a bug? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1511) Upgrade tm-extractors jar
[ https://issues.apache.org/jira/browse/JCR-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584471#action_12584471 ] Paco Avila commented on JCR-1511: - Ok, good point. > Upgrade tm-extractors jar > - > > Key: JCR-1511 > URL: https://issues.apache.org/jira/browse/JCR-1511 > Project: Jackrabbit > Issue Type: Improvement > Components: jackrabbit-text-extractors > Reporter: Paco Avila > > There is a new version of tm-extractors in http://www.textmining.org/ which > some improvements. This upgrade need some refactoring in the class > MsWordTextExtractor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1511) Upgrade tm-extractors jar
Upgrade tm-extractors jar - Key: JCR-1511 URL: https://issues.apache.org/jira/browse/JCR-1511 Project: Jackrabbit Issue Type: Improvement Components: jackrabbit-text-extractors Reporter: Paco Avila There is a new version of tm-extractors in http://www.textmining.org/ which some improvements. This upgrade need some refactoring in the class MsWordTextExtractor.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1482) Jackrabbit web page scroll is slow with Firefox
[
https://issues.apache.org/jira/browse/JCR-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579759#action_12579759
]
Paco Avila commented on JCR-1482:
-
Thank you for fixing it :)
> Jackrabbit web page scroll is slow with Firefox
> ---
>
> Key: JCR-1482
> URL: https://issues.apache.org/jira/browse/JCR-1482
> Project: Jackrabbit
> Issue Type: Wish
> Components: jackrabbit-site
> Environment: Firefox 2.0.0.12 in Ubuntu 7.10 - Gutsy Gibbon
>Reporter: Paco Avila
>Assignee: Jukka Zitting
> Fix For: none
>
>
> When I visit http://jackrabbit.apache.org/ from my Firefox in Ubuntu the
> browser scroll is very slow and make CPU go to 100%.
> The problem seems to be the "fixed" attribute in the css background
> definition, so it should be removed.
> body {
> background:white url(bg.png) repeat-x fixed center bottom;
> font-family:Verdana,Helvetica,Arial,sans-serif;
> font-size:small;
> margin:0pt;
> padding:0pt;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1482) Jackrabbit web page scroll is slow with Firefox
Jackrabbit web page scroll is slow with Firefox
---
Key: JCR-1482
URL: https://issues.apache.org/jira/browse/JCR-1482
Project: Jackrabbit
Issue Type: Wish
Components: jackrabbit-site
Environment: Firefox 2.0.0.12 in Ubuntu 7.10 - Gutsy Gibbon
Reporter: Paco Avila
When I visit http://jackrabbit.apache.org/ from my Firefox in Ubuntu the
browser scroll is very slow and make CPU go to 100%.
The problem seems to be the "fixed" attribute in the css background definition,
so it should be removed.
body {
background:white url(bg.png) repeat-x fixed center bottom;
font-family:Verdana,Helvetica,Arial,sans-serif;
font-size:small;
margin:0pt;
padding:0pt;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
