Dynamically Register Event Handlers Fast For Saved Data

Tim__D

I have a DCT where the same field exists in the DCR at many different places.

Example: where X is the item to register events

/root/X
/root/container/X
/root/item/container/item/X
/root/item/container/X

To register event handlers for all these locations of item "X" today I have the following:
IWEventRegistry.addItemHandler(/root/X.........................................
IWEventRegistry.addItemHandler(/root/container/X...............................
IWEventRegistry.addItemHandler(/root/item/container/item/X.....................
IWEventRegistry.addItemHandler(/root/item/container/X..........................

Is there a way to do something similar to xpath where I could just say
IWEventRegistry.addItemHandler(//X

I need it to perform well for large DCR's that have been previosuly saved so trawling through the content onFormInit() and registering the events as item X is found may not meet the performance requirement.

Adding handlers using the available API is fine when adding replicants would be fast enough but the events need to be on existing saved elements when saved data is edited. The long method noted above works but in highly recursive DCR sachems there must be a better way.

ISCBorisB

I have a DCT where the same field exists in the DCR at many different places. Example: where X is the item to register events /root/X /root/container/X /root/item/container/item/X /root/item/container/X To register event handlers for all these locations of item "X" today I have the following: IWEventRegistry.addItemHandler(/root/X......................................... IWEventRegistry.addItemHandler(/root/container/X............................... IWEventRegistry.addItemHandler(/root/item/container/item/X..................... IWEventRegistry.addItemHandler(/root/item/container/X.......................... Is there a way to do something similar to xpath where I could just say IWEventRegistry.addItemHandler(//X I need to to perform well for large DCR's that have been previosuly saved so trawling through the content onFormInit() and registering the events as they are found may not meet the performance requirement. Adding handlers using the available API is fine when adding replicants and would be fast enough but the events need to be on existing saved elements when saved data is edited. The long method works but in highly recursive DCR sachems there must be a better way.

I can think of couple approaches to try, not sure if either will work though...

1. Try some DCT level inline command. Get / parse Type's datacapture.cfg there and prepare *something*
(JS Array of required XPath elements for example) for the future usage on init Event. On init simply
register required events for the collection.

Issues: what and how to pass. I'm not sure if inlines can even create script Tag substitution(s).
If it can't you'll need artificial way of passing the list like hidden item description or some such.

2. Use undocumented Event Listeners rather than event Registry. In this approach you register
certain Event handler(s) only once. It is then Handler's responsibility to figure out which Item
caused the Event and decide to either process or ignore it.

Issues:
- All the usual hack-related considerations
- You'd have to find out if required Event(s) even have a corresponding Listener (most do or did, anyway)
- Within your TS Version you'd have to figure out how to determine Event Source XPath. Note that this mechanism
has been introduced in 6.1, IWItem and other familiar Classes were not yet present, etc...

See if [thread=20870]this[/thread] and [thread=21999]this[/thread] threads may help a little