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=17950>. 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=17950 Defect of the jax-rpc handler impl on the processing model ------- Additional Comments From [EMAIL PROTECTED] 2003-03-14 17:04 ------- Hi Sreekant, Thanks for your backup on this thread. I'd like to make an answer to your comments. | Toshi, It would be nice if you can add an IndexOutOfBoundsException |check just to avoid configuration errors, in which case system can |revert back to default. This request has been expected, but I don't want to handle the check on the runtime because of the performance issue. The check is required just one time when the handler chain is configured by a user. So, I designed that the check logic would be implemented in the admin tool rather than the runtime routine. If the patch had fully committed, I would propose a new patch of the checking logic for the deployment admin tool. | If I am not missing anything, patch you presented here doesn't handle |"-1" case (Rule 'd'). In this case some one has to generate response |message and hand it to transport chain. I think it works well if you set up the 'onFalseRestartAt' as '-1' with my original patch. In that case, the handleRequest method what returns false has to make a response massage as described on the spec. Best Regards, Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]> R&D Headquarters NTT DATA Corporation
