2010/1/25 Geert Josten <[email protected]>: > Hi Andrew, > >> Instead of making the range index on <e:date> I will make it >> on a custom element, say <my:date>. Then after the cpf has >> finished, as an on-modify trigger, I can go through the >> <e:date> elements and where they are castable as xs:date >> convert them to <my:date>, and where they aren't just remove >> the markup. > > You could append a pipeline of your own after the current CPF processes. > Writing an action that loops through all e:date elements, attempts casting to > xs:date and convert to a my:date if it works should be very difficult. If you > need any help, just let us know.. >
Thanks - for a similar task (adding lat and long attributes to e:gpe elements) I was using a custom pipeline however I had a few issues with ensuring the step ran last (that will be a question for another day :) When whatever task you are doing needs to run after the CPF has finished then I guess its a reasonable approach to use a post-commit on-modify trigger. -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/ _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
