Hi all,

after a long (weeks!) on and off debugging session between my development 
environment and the customer's deployment I finally found the issue. This might 
interest others here and then I have a related question.

D2W application with one rule file with some 600+ rules, development on Lion 
with Eclipse/WOlips 3.4, deployment on Solaris

Problem:
------------
Customer complained that some things did not work correctly that are supposed 
to be set from the rules. It worked in my environment but not at the 
customer's. Cross checked all rules, compared rule file, cleaned and 
regenerated app - it worked. Great, must have been some stuff hanging around 
that got cleaned. Continued working, giving next revision to customer -> 
sometimes similar problems. Some rules obviously just not firing.

Solution:
-----------
Eventually I found one or two rules that were identical on the LHS (including 
priority) but RHS was different. Thus it was clear that depending on outside 
temperature and constellation of the stars sometime one or the other rule 
fired. As the rule file was constantly updated and rewritten the situation 
changed every time. After finding the duplicate and removing it everything was 
stable.

QUESTION:
---------------
Is there a tool that helps finding such duplicate contradicting rules? There 
might be more lurking in the rule file and eventually causing headache. How are 
you dealing with such a case? Duplicate rules can probably not really be 
avoided as one is trying things out during development. Displaying the rules in 
RuleModeler sorted LHS and checking visually for duplicates is not feasible 
because some rules are very long and a 50" screen would be needed (sorry, 
haven't one)

Thanks for help/ideas

---markus---


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to