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-13 15:24 ------- Dims, Spec only talks abt the default case (where the response flow starts from the handler that returned false). Being able to customize the response flow in this scenario gives a more flexible and adaptable handler chain flow management. Solution presented over here will allow the user to specify starting point in the configured service response flow. Response flow would start at this point and will traverse the configured chain. This is one way of customization user can be endowed with. I believe that this gives fair enough control over handler chain. There could be some other customizations. 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. 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. Regards, Sreekant
