| Right off the bat I'd say try to get rid of the eval usage. Can you put the phone number into an object like this: class PhoneNumber { private char digit0; private char digit1; ///...same for the rest of the digits public char getDigit0() { return digit0; } public char getDigit1() { return digit1; } } Then the conditions would look like this: digit0 == '$param' Behind the scenes hopefully this will optimize better. The use of eval won't optimize well. Are you using sequential mode? This might be a good candidate for that if setting the price does not trigger any other rules to fire. --- On Fri, 5/14/10, Antonio Anderson Souza <antonioams@gmail.com> wrote:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||