[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Attachment: src-ocm-ext.rar An experimental implementation of lifecycle callback. Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin Attachments: src-ocm-ext.rar It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Attachment: (was: src-ocm-ext.rar) Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Attachment: src-ocm-ext.rar An experimental implementation of lifecycle callback feature. Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin Attachments: src-ocm-ext.rar It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Comment: was deleted Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin Attachments: src-ocm-ext.rar It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Attachment: (was: src-ocm-ext.rar) Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Comment: was deleted Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1908) Add lifecycle callback feature
[ https://issues.apache.org/jira/browse/JCR-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zha zhengyin updated JCR-1908: -- Attachment: src-ocm-ext.rar An experimental implementation of lifecycle callback feature. Add lifecycle callback feature -- Key: JCR-1908 URL: https://issues.apache.org/jira/browse/JCR-1908 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-ocm Reporter: zha zhengyin Attachments: src-ocm-ext.rar It would be useful to add lifecycle callbacks in OCM like the JPA or hibernate does so we can perform such tasks as logging, validating data, auditing,sending notifications etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JCR-1909) Property collectionClassName of CollectionDescriptor is never used
Property collectionClassName of CollectionDescriptor is never used Key: JCR-1909 URL: https://issues.apache.org/jira/browse/JCR-1909 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-ocm Affects Versions: 1.6.0 Reporter: Sandrine Raffalli Line 787 of ObjectConverterImpl : Class collectionFieldClass = ReflectionUtils.getPropertyType(object, collectionDescriptor.getFieldName()); The collection field class is always determined by reflection and never with the property collectionClassName of CollectionDescriptor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Does OCM suppport lifecycle callback?
This kind of features is not yet supported but there is a plan to do it. we should start a Jira issue to find a good solution for this kind of problem. br, Christophe On Fri, Dec 12, 2008 at 08:08, Yonder zy...@yahoo.com.cn wrote: nt:unstructured allows any number of properties with any names. but with OCM, we can only set predefined properties on a jcr node. It's not flexible sometime. for example, a CmsObject may have some optional properties then user can place owner information or something else. Maybe we can add a callback feature in ObjectConverterImpl that allows some annotated methods in an ocm object will be callback during saving or retrieving the object ___ 好玩贺卡等你发，邮箱贺卡全新上线！ http://card.mail.cn.yahoo.com/
Re: [CONF] Apache Jackrabbit: Privacy Policy (page created)
Hi, On Fri, Dec 12, 2008 at 11:06 AM, conflue...@apache.org wrote: Privacy Policy (JCR) created by Jukka Zitting http://cwiki.apache.org/confluence/display/JCR/Privacy+Policy This is the result of discussion [1] on the legal-discuss@ mailing list. I'm still pursuing a resolution to all the issues raised about Google Analytics, but the privacy policy should already address the most pressing one (the GA terms of service require that we post such a policy). I'll also try to set up a process that periodically exports the GA reports for anyone to view. As an example, see [2] for a nice report that shows the peak of interest generated by the 1.5.0 release. For comparison, the peak with Jackrabbit 1.4 was below 2k daily visits. [1] http://markmail.org/message/q6wzbv7jx2zsvi64 [2] http://people.apache.org/~jukka/jackrabbit/GA-20081211.pdf BR, Jukka Zitting
Re: Jackrabbit board report draft
On Fri, Dec 12, 2008 at 11:45 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: o Community Claus Köll joined the Jackrabbit team as a committer and PMC member. The slump in community activity over late summer seems to be gone and we're back to normal levels of mailing list and commit activity. We are considering to start a JCR Commons subproject for managing the development and release of a number of our components that are not tightly coupled with the Jackrabbit content repository implementation. This subproject would keep using our existing mailing lists but would have its own web site (under http://jackrabbit.apache.org/commons/) and separate issue trackers and release cycles for each component. See http://markmail.org/message/qqlvlwpgi5oauak6 for more details. o Development Development in trunk continues with post-1.5 features, and I expect us to release Jackrabbit 1.6 early next year. Jackrabbit 2.0 (and the JSR 283 reference implementation) will probably be released later next year. I would add that we opened up the Jackrabbit Sandbox for all Apache committers and that this was triggered by the recent interest (and development start) of an implementation of the upcoming CMIS standard backed by JCR. Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com
Jackrabbit board report draft
Hi, Here's a draft of the quarterly report that I plan to submit to the ASF board. Let me know if you have anything to add or modify. draft Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We released Apache Jackrabbit 1.5.0 on December 8th. We also made the following patch releases from the 1.4 branch: * jackrabbit-core 1.4.6 on October 7th * jackrabbit-classloader 1.4.1 on October 2nd * jackrabbit-jcr-server 1.4.1 on September 30th o Legal We use Google Analytics to track usage of our web site. We posted a privacy policy that mentions the Analytics use on our web site and continue to work with legal-discuss@ to resolve concerns that were raised about the use of Google Analytics. o Community Claus Köll joined the Jackrabbit team as a committer and PMC member. The slump in community activity over late summer seems to be gone and we're back to normal levels of mailing list and commit activity. We are considering to start a JCR Commons subproject for managing the development and release of a number of our components that are not tightly coupled with the Jackrabbit content repository implementation. This subproject would keep using our existing mailing lists but would have its own web site (under http://jackrabbit.apache.org/commons/) and separate issue trackers and release cycles for each component. See http://markmail.org/message/qqlvlwpgi5oauak6 for more details. o Development Development in trunk continues with post-1.5 features, and I expect us to release Jackrabbit 1.6 early next year. Jackrabbit 2.0 (and the JSR 283 reference implementation) will probably be released later next year. o Infrastructure No issues at the moment. /draft BR, Jukka Zitting
Re: Jackrabbit board report draft
Hi, On Fri, Dec 12, 2008 at 1:39 PM, Alexander Klimetschek aklim...@day.com wrote: I would add that we opened up the Jackrabbit Sandbox for all Apache committers and that this was triggered by the recent interest (and development start) of an implementation of the upcoming CMIS standard backed by JCR. Good point, I totally missed that. Thanks! BR, Jukka Zitting
Re: Jackrabbit board report draft
Hi, On Fri, Dec 12, 2008 at 2:05 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Good point, I totally missed that. Thanks! Here's an updated version: draft Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR, specified in JSR 170). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We released Apache Jackrabbit 1.5.0 on December 8th. We also made the following patch releases from the 1.4 branch: * jackrabbit-core 1.4.6 on October 7th * jackrabbit-classloader 1.4.1 on October 2nd * jackrabbit-jcr-server 1.4.1 on September 30th o Legal We use Google Analytics to track usage of our web site. We posted a privacy policy that mentions the Analytics use on our web site and continue to work with legal-discuss@ to resolve concerns that were raised about the use of Google Analytics. o Community Claus Köll joined the Jackrabbit team as a committer and PMC member. The slump in community activity over late summer seems to be gone and we're back to normal levels of mailing list and commit activity. Based on interest to the CMIS implementation effort (see below), we have extended write access in our sandbox area in svn to all Apache committers. We are considering to start a JCR Commons subproject for managing the development and release of a number of our components that are not tightly coupled with the Jackrabbit content repository implementation. This subproject would keep using our existing mailing lists but would have its own web site (under http://jackrabbit.apache.org/commons/) and separate issue trackers and release cycles for each component. See http://markmail.org/message/qqlvlwpgi5oauak6 for more details. o Development Development in trunk continues with post-1.5 features, and I expect us to release Jackrabbit 1.6 early next year. Jackrabbit 2.0 (and the JSR 283 reference implementation) will probably be released later next year. A new sandbox component was started for an effort to implement the proposed Content Management Interoperability Services (CMIS) specification on top of a JCR content repository. o Infrastructure We created a new Jira project (JCRCMIS) for the CMIS implementation effort and plan to create more assuming the JCR Commons subproject gets started. We've enabled wiki markup and the patch-available workflow in the JCRCMIS project. If these features work well, we will enable them also in our main JCR Jira project. /draft BR, Jukka Zitting
[jira] Created: (JCR-1910) RMIRemoteBindingServlet fails to initialize if the RMI registry is not available
RMIRemoteBindingServlet fails to initialize if the RMI registry is not available Key: JCR-1910 URL: https://issues.apache.org/jira/browse/JCR-1910 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-jcr-rmi Affects Versions: 1.5.0 Reporter: Jukka Zitting Assignee: Jukka Zitting Fix For: 1.5.1 If the RMI registry is not available, the RMIRemoteBindingServlet in jcr-rmi will throw an exception in the init() method and prevent the servlet from being loaded. The same servlet can however also be mapped to the normal HTTP URL space as an alternative mechanism of making the RMI endpoint available to clients. Thus it would be better if the init() method just logged a warning instead of failing completely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jackrabbit board report draft
On 12 Dec 2008, at 23:55, Jukka Zitting wrote: Claus Köll joined the Jackrabbit team as a committer and PMC member. The slump in community activity over late summer seems to be gone and we're back to normal levels of mailing list and commit activity. How is the ratio of day developer to non-day developers for jackrabbit and sling now? I think getting more external committers was one of the requirements to get sling out of incubator status? -- Torgeir Veimo torg...@pobox.com
Re: Jackrabbit board report draft
Hi, On Fri, Dec 12, 2008 at 3:21 PM, Torgeir Veimo torg...@pobox.com wrote: How is the ratio of day developer to non-day developers for jackrabbit and sling now? I think getting more external committers was one of the requirements to get sling out of incubator status? The ratio of Day/non-Day committers is 12/11 in Jackrabbit and 3/5 in Sling. The picture in commit activity is a bit different: The ratio of Day/non-Day committers who've made a commit within the past six months (i.e. are at least somewhat active) is 10/6 in Jackrabbit and 3/1 in Sling. In both projects the amount of individual commits is heavily dominated by commits from Day employees who are paid for working directly on these projects. BR, Jukka Zitting
Re: Cannot get full-text searching to work
I sometimes search using multiple key words; I observe that results are consistent and does not return results as expected. I save a jcr:data node with the string --This is Content one I do a search with the following query //*[jcr:contains(.,'Content') and jcr:contains(.,'one')] I expect 1 match but get 0; The I overwrite jcr:data with -- Test Content one I do a search with the following query //*[jcr:contains(.,'Content') and jcr:contains(.,'one')] I expect 2 but get 1 I again overwrite jcr:data with -- Test others I expect 0 but still get 1 I then persist the following The jcr:data contains a String This is Content one and hence I expected the result set to contain one node but I got zero results back. Is my query correct? Alexander Klimetschek wrote: On Mon, Dec 8, 2008 at 11:13 PM, pkrishna prabhakar.krishnasw...@ge.com wrote: String query = //*[jcr:contains(jcr:content, 'Test')]; String query = //jcr:content[jcr:contains(., 'Test')]; The first argument of jcr:contains() is either ., which refers to the local node and by default means all properties of the current node (you can configure that, see the aggregation in [1]), or can be the name of a property, prefixed with an @. So your query probably should look like: //*[jcr:contains(., 'Test')] This will give you back all jcr:content nodes. If you want to retrieve the parent nodes, you can change the aggregation to include the jcr:content subnode and its properties for your ecr:ecisContentItem nodes [1]. For the definition of the jcr:contains function, see section 6.6.5.2 of the JCR 1.0 spec [2]. [1] http://wiki.apache.org/jackrabbit/IndexingConfiguration [2] http://jcp.org/en/jsr/detail?id=170 Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com -- View this message in context: http://www.nabble.com/Cannot-get-full-text-searching-to-work-tp20904596p20985882.html Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
