http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20987 Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.bundle.MySqlPersistenceManager: Access denied for user 'root'< at >'localhost' (using password: NO): Access denied for user 'root'< at >'localhost' (using password: NO) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JCR-1899 URL: https://issues.apache.org/jira/browse/JCR-1899 Project: Jackrabbit Issue Type: Bug Reporter: Narender pls help me am integrate jackrabbit+spring while reading the repository.xml file am getting error . Context file <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:util="http://www.springframework.org/schema/util" xsi:schem Narender (JIRA 2008-12-05T04:06:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20986 Hi, Thanks for all the comments, keep 'em coming! Here's an updated version of the JCR Commons subproject proposal. This version should address most of the concerns and issues that were raised. COMPONENTS The JCR Commons subproject would take over the development and maintenance of the following components: * jackrabbit-parent * jackrabbit-jcr-tests * jackrabbit-jcr-benchmark * jackrabbit-jcr-rmi * jackrabbit-jcr-servlet * jackrabbit-classloader * jackrabbit-ocm * jackrabbit-ocm-nodemanagement Most notably (and a bit surprisingly), the jcr-commons component would remain with the core project for now to avoid complicating the development workflow for issues that may range over component boundaries. We may need to split the jcr-commons component to be able to move parts of the code to the proposed subproject, but that's a separate discussion that we don't need to solve now. Similarly, the jcr-server and webdav components will be kept with core for now until we have better idea abo Jukka Zitting 2008-12-04T15:40:10 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20985 [ https://issues.apache.org/jira/browse/JCR-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653328#action_12653328 ] Marcel Reutegger commented on JCR-1885: --------------------------------------- Oops, wrong default value... Fixed in revision: 723346 Marcel Reutegger (JIRA 2008-12-04T15:20:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20984 [ https://issues.apache.org/jira/browse/JCR-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-1898: ---------------------------------- Attachment: JCR-1898.patch Proposed patch. Marcel Reutegger (JIRA 2008-12-04T15:16:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20983 Replace customized QueryParser.jjt ---------------------------------- Key: JCR-1898 URL: https://issues.apache.org/jira/browse/JCR-1898 Project: Jackrabbit Issue Type: Improvement Components: jackrabbit-core Reporter: Marcel Reutegger Priority: Minor We should rather use the Lucene default and implement a Jackrabbit version that extends from it. This eases maintenance when moving from one Lucene version to another. Marcel Reutegger (JIRA 2008-12-04T14:17:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20982 [ https://issues.apache.org/jira/browse/JCR-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653294#action_12653294 ] Alexander Klimetschek commented on JCR-1897: -------------------------------------------- Which version of Jackrabbit are you using? Important for this errors are the jars jackrabbit-core-*.jar and jackrabbit-jcr-commons-*.jar (which contains ValueFactoryImpl). Looks like a (very old) version mismatch - the getInstance method was added in JCR-473. Alexander Klimetschek (JIRA 2008-12-04T13:23:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20981 [ https://issues.apache.org/jira/browse/JCR-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-1896. --------------------------------- Resolution: Invalid You have a typo: org.apache.jackrabbit.core. instead of com.iorga.jackrabbit.core. Thomas Mueller (JIRA 2008-12-04T09:29:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20980 java.lang.NoSuchMethodError: org.apache.jackrabbit.value.ValueFactoryImpl.getInstance()Ljavax/jcr/ValueFactory -------------------------------------------------------------------------------------------------------------- Key: JCR-1897 URL: https://issues.apache.org/jira/browse/JCR-1897 Project: Jackrabbit Issue Type: Bug Reporter: Narender Am new to Jackrabbit. am integrating spring+jackrabbit.. am getting error NoSuchMethodError: org.apache.jackrabbit.value.ValueFactoryImpl.getInstance()Ljavax/jcr/ValueFactory; Caused by: java.lang.NoSuchMethodError: org.apache.jackrabbit.value.ValueFactoryImpl.getInstance()Ljavax/jcr/ValueFactory; Please help me.... log4j:WARN No appenders could be found for logger (org.springframework.context.support.ClassPathXmlApplicationContext). log4j:WARN Please initialize the log4j system properly. Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean wit Narender (JIRA 2008-12-04T07:00:45 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20979 Persistence Manager Issue ------------------------- Key: JCR-1896 URL: https://issues.apache.org/jira/browse/JCR-1896 Project: Jackrabbit Issue Type: Bug Affects Versions: core 1.4.5 Environment: Windows Server 2003 Tomcat Apache Reporter: Norman Sheriff <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN" "http://jackrabbit.apache.org/dtd/repository-1.2.dtd"> <Repository> <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem"> <param name="path" value="${rep.home}/repository" /> </FileSystem> <Security appName="Jackrabbit"> <AccessManager class="org.apache.jackrabbit.core.security.SimpleAccessManager"></AccessManager> <LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule"> <param name="anonymousId" value="anonymous" /> </LoginModule> </Security> <Workspaces rootPath="${rep.home}/workspaces" defaultWo Norman Sheriff (JIRA 2008-12-03T18:13:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20978 [ https://issues.apache.org/jira/browse/JCR-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandrine Raffalli updated JCR-1895: ----------------------------------- Description: In the DefaultCollectionConverter in the insert method : if the element has an identifier field it's this field that is taken as the elementJcrName. Else it is the jcrElementName of the collection or the default name. In the update method, if the element has an id field and an uuid field, it's the jcrElementName of the collection or the default name that is taken, not the id field. In case of insert or update, it must take the same identifier to build the path. was: In the DefaultCollectionConverter in the insert method : if the element has an identifier field it's this field that is took for the elementJcrName. Else it is the jcrElementName of the collection or the default name. In the update method, if the element has an id field and an uuid field, it's the jcrElementName of the collection Sandrine Raffalli (JIRA 2008-12-03T15:59:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20977 Different behavior with insert and update of a collection --------------------------------------------------------- Key: JCR-1895 URL: https://issues.apache.org/jira/browse/JCR-1895 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-ocm Affects Versions: 1.6.0 Reporter: Sandrine Raffalli In the DefaultCollectionConverter in the insert method : if the element has an identifier field it's this field that is took for the elementJcrName. Else it is the jcrElementName of the collection or the default name. In the update method, if the element has an id field and an uuid field, it's the jcrElementName of the collection or the default name that is took, not the id field. In case of insert or update, it must take the same identifier to build the path. Sandrine Raffalli (JIRA 2008-12-03T15:53:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20976 Hi, On Wed, Dec 3, 2008 at 11:45 AM, Alexander Klimetschek <aklimets< at >day.com> wrote: The jcr-commons component has a long history of being more a collection of utilities for jackrabbit-core than a real standalone collection of commons code. Perhaps it would make more sense to rename the component to jackrabbit-util and just move the more recent stuff under org.apache.jackrabbit.commons to the proposed new JCR Commons subproject. I would rather avoid doing that. We should IMHO only have SNAPSHOT dependencies within components that are included in the same build. BR, Jukka Zitting Jukka Zitting 2008-12-03T13:27:01 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20975 [ https://issues.apache.org/jira/browse/JCR-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652775#action_12652775 ] Marcel Reutegger commented on JCR-1855: --------------------------------------- There's a bug in Lucene that blocks us from upgrading: https://issues.apache.org/jira/browse/LUCENE-1474 Marcel Reutegger (JIRA 2008-12-03T13:15:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20974 hi jukka it isn't a problem but it can be pretty cumbersome if fixes/improvements made to any of the commons project are floating around waiting for the next release cycle (that takes forever for some reason or the other) and i need to use them already in the core modules (basically that was the reason why the issue was detected at all)... in that situation i will have to wait for the next release or locally adjust the pom setting the dependency to the current commons snapshot. that latter is pretty much error prone, i'd say. angela Angela Schreiber 2008-12-03T10:53:23 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20973 +1 Christophe On Tue, Dec 2, 2008 at 11:24, Jukka Zitting <jukka.zitting< at >gmail.com> wrote: Christophe Lombart 2008-12-03T10:58:01 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20972 Well, I guess jcr-commons should really be part of the commons subproject, as it is supposed to help with the jcr api in general. And nothing could hinder us from using a snapshot dependency on jcr-commons in the trunk of core - we only have to take care and release jcr-commons before a new core release. Regards, Alex Alexander Klimetschek 2008-12-03T10:45:25 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20971 Hi, On Wed, Dec 3, 2008 at 9:13 AM, Angela Schreiber <anchela< at >day.com> wrote: OK, that's fine. We could keep jcr-server with the core for now and decide later if or when it should be moved to the commons. That should still be possible, though with one caveat: the latest version of jcr-commons in the build would now be the latest _released_ version. Similarly, in jcr-server the latest version of the webdav component would be the latest webdav release. Is this a problem? If yes, then we could keep such upstream dependencies with the core for now, only moving those components that aren't really related to changes in core components. That would leave us with: * jackrabbit-jcr-tests * jackrabbit-jcr-benchmark * jackrabbit-jcr-rmi * jackrabbit-jcr-servlet * jackrabbit-classloader * jackrabbit-ocm * jackrabbit-ocm-nodemanagement BR, Jukka Zitting Jukka Zitting 2008-12-03T10:36:09 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20970 Word doc extraction problem --------------------------- Key: JCR-1894 URL: https://issues.apache.org/jira/browse/JCR-1894 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-text-extractors Affects Versions: core 1.4.3 Environment: OS: Windows 2003 sp2 My-eclipse6.0 / tomcat 5.5 and Athelon500+ Reporter: Rajesh Upadhyay Hi, I have a .doc file which contains data inside a table. Now i want to parse the table to get the table values. Normal Parsing is not working for table( I mean using String tokenizer) because it is giving some unwanted special characters while parsing the table. So I just want to convert that .doc to .txt file, then only it is easy to split the values. But i can't make it! Can any one please tell me how to parse a MS WORD TABLE Values? We need to know the process by which we can index a doc file excluding special characters, When we will show the excerpt then these special characters make Rajesh Upadhyay (JIRA 2008-12-03T10:29:44 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20969 hi jukka that has been discussed in the past and honestly i don't want to start that discussion again. as long as there are no other active contributers than julian and myself i don't see any need to move the webdav project somewhere else. regarding jcr-server: i think we should address JCR-417 first instead of putting the complete jcr-server to a commons project, since i have the feeling the server part of the jcr-remoting doesn't really belong to the commons. apart i don't have any strong feelings regarding the commons stuff unless i can run a single mvn call to built and test all of jackrabbit-core and the various spi projects with the latest version of jackrabbit commons and without having to touch the pom. angela Angela Schreiber 2008-12-03T08:13:35 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20968 No, it would be a WebDAV + CMIS connector then. The only overlap probably is addressing/mapping (between HTTP resources and JCR nodes), GET and PUT -- but I think it would be good to have those in a single place. BR, Julian Julian Reschke 2008-12-02T19:48:16 http://permalink.gmane.org/gmane.comp.apache.jackrabbit.devel/20967 very good point! this also puts us into a good position to file issues for the CMIS jira ;) regards, david David Nuescheler 2008-12-02T19:31:48 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.jackrabbit.devel