DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12997>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12997 Call the method as soon as the last parameter is encountered ------- Additional Comments From [EMAIL PROTECTED] 2003-09-22 06:54 ------- Following Craig's suggestion re some test cases to check for CallMethodRule invocation order, I attach a very simple change to an existing test. The patch also includes some minor javadoc tidyups in the test classes. I believe that this enhanced test would report failure if Emmanuel's proposed was applied (changing CallMethodRule firing order), unlike the existing test, which would not report failure. I have not verified this by applying the patch, as I was not able to get it to apply cleanly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
