thanks for this; In my case, using the DAV:modificationdate had lots of problems - i cant run the touch tool without those values changing!
I agree that in general this shouldn't be needed, but in my case I needed to have the dates that webdav had create for publication dates, and inject them so that I could have the displayed publication dates not tied to the webdav modification date. I should have had these nodes from the start. -Toolman On Fri, 2008-05-23 at 14:37 +0200, Ard Schrijvers wrote: > Hello Toolman, > > I am not really keen on content duplication, where extracting content > into webdav properties is already some sort of duplication, meant for > fast searching/retrieving. > > Putting webdav properties back into the xml, is IMHO completely > obsolete: you already have that value, namely in the webdav property, > which you can just retrieve from the document, just as you fetch the > content of the document. For fast searching is serves no purpose. > > Also, you have a catch22, because after saving the value into your xml > /document/content/datum, the modificationdate changes again :-) Perhaps > you setting the /datum with some granularity, like on days, so you > wouldn't notice. But, IMO, your heading the wrong way. > > I did not look at your code, but quite frankly, I don't think I will > ever want to do the thing you are doing, for the reasons mentioned > above. > > I still do like your input, suggestions, improvements, but I have to be > critical :-) Perhaps my reasons might convince you to attack your issue > by a different approach, > > Regards Ard > > > > > Hello guys; > > > > I am posting a batch plugin I wrote to help out with a > > specific problem I had. Again, hope this helps someone. > > > > Hippo guys, maybe you want to pick this up and give it a good cleanup? > > > > It does a very specific task; read the last modificationdate, > > and injects that into the content at the node /document/content/datum. > > > > This is a very specific bit of code that would need tweaking > > for anyone else to use (usefully), but its pretty easy to > > change. Sorry for all the System.outs and hard codedness - > > not great code by any strech. > > > > No warranty or guarantees! > > > > > > Toolman > > > > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
