Hi Jukka, Here is the exact scenario " The application publishes (to some predefined location in a file system) the content of the repository irrespective of Node added, updated or deleted. Now this is not done to all the files, only some of the selected ones(depending upon the publish property set inside jcr:content). So when i update or add new nt:file node, I can always read those custom property which decides whether to publish the file on the file system.
I was assuming that the version history still remains intact eventhough you remove the versionable node from the repository. So if somehow if i can get a handle to the version history of that actual node, then i can pull out the property "publish" so that if set true i can publish the deleted file on to some specific file location. Hope this would give little bit of idea about my application. thanks, Sudhan Jukka Zitting wrote: > > Hi, > > On 4/10/07, Sudhan <[EMAIL PROTECTED]> wrote: >> My scenario is that, I am already setting some custom property on all the >> jcr:content node during initialization. Now this property is useful when >> there are any new updates on the node aswell as when the node is removed >> from the repository. >> >> So when i get an event for NODE_REMOVED, I need to pull out the property >> set >> on jcr:content node of the deleted node. I had a notion that the version >> history still remains eventhough you remove the node from the repository. >> Now my problem is to get a handle to jcr:content node and do some >> processing >> after getting the property. > > I'm not sure I follow you. Isn't the jcr:content node removed as well > when the containing node gets removed? Thus there is no way for you to > set any jcr:content properties after the removal. > > BR, > > Jukka Zitting > > -- View this message in context: http://www.nabble.com/Getting-Version-History-after-the-node-is-deleted-tf3549983.html#a9940963 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
