FWD » Core Development » Conversion Tools

This rule set was incorrectly placed in TIMCO's pattern/ directory. It has nothing TIMCO-specific in it. Please move it into the standard location and change its name to "standard_customer_specific_tools.rules". That will make the purpose more obvious.

Then you will have to change the core_conversion.xml to load it (non-optionally). You can leave the customer_specific_conversion.rules as an optional rule-set. I suspect it should be optionally loaded before the standard_customer_specific_tools.rules. Please add a feature to standard_customer_specific_tools.rules that will bypass processing for a customer_specific node if it is marked with a particular boolean annotation named "handled". That will allow the customer_specific_conversion.rules to override the behavior in standard_customer_specific_tools.rules since it can process something however it wants and then it can mark the node with that annotation, causing standard_customer_specific_tools.rules to bypass the node.

Finally, please review the standard "tools" currently provided by this rule-set. If there are any obvious changes or improvements that should be made, please make the changes. It is OK to break the current "contract" of the tools so long as you fix it up in the TIMCO customer_specific_annotations_prep.rules, such that the result is the same.

The overall objective is to ensure that a standard set of tools is always there in the conversion environment AND that a given project can still make overrides as needed.

Sent final updates for review (for both P2J and TIMCO projects). The other_customization.odt and managing_changes.odt were updated, the new info was bracketed in [CA] ... [/CA] tags.