<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=544025104-07052006><FONT face=Arial size=2>I'm handling
CmsEvents in order to modify a resource's properties based on its contents every
time those contents change. Can anyone suggest the best mix of event and
resource state to use? So far it's looking like
I_CmsEventListener.EVENT_RESOURCE_MODIFIED (and I guess
I_CmsEventListener.EVENT_RESOURCES_MODIFIED) when the resource's state is '1'
(i.e. CmsResource.STATE_CHANGED). I'll probably also listen for property
changes too, just to ensure that the contents and associated properties really
are kept in synch.</FONT></SPAN></DIV>
<DIV><SPAN class=544025104-07052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=544025104-07052006><FONT face=Arial size=2>The trouble with
carrying out actions on meeting EVENT_RESOURCE_MODIFIED and STATE_CHANGED is
that two matching events seem to be fired when a user edits then publishes a
resource directly. Maybe I don't have a choice, but it's a pity that I end
up carrying out the same modifications twice.</FONT></SPAN></DIV>
<DIV><SPAN class=544025104-07052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=544025104-07052006><FONT face=Arial size=2>The resources
concerned are of custom XML types. I can't use the
usual element-to-properties mapping mechanism because the mapping isn't
straightforward; and in any case, having full control over the mapping seems
like a nice way of getting around the problem mentioned in the thread "Several
Languages - Howto" started by Roman Uhlig last October.</FONT></SPAN></DIV>
<DIV><SPAN class=544025104-07052006></SPAN> </DIV>
<DIV><SPAN class=544025104-07052006><FONT face=Arial
size=2>Jon</FONT></SPAN></DIV></BODY></HTML>