Hi,
5. Again, as Ajith mentioned also, we do not know the handler chain before hand. IIRC, we have templates of handler chains and we clone from it to get the fixed set of handlers. But after that we need to include service and operation specific handlers. Ajith, yes we do have service specific handlers and it is useful. For example engaging modules per service basis using WS-Policy. It is not just a "possible" use case, people do use it.
Thanks for the clarification :) I was actually thinking more of the operation specific handlers. I believe the reason why we replicate that handler chain at the operation level is to support not just service specific handlers but also operation specific handlers. Now that I've taken a closer look again at the things, I see that we provide the functionality to engage specific modules 'per operation' (in which case a operation specific handler chain is needed). Anyway there is always the possibility that a user may need his/her own handlers to be engaged per operation. However we may be able to improve a bit of the code :) Since the handlers are stateless replicating them would not mean anything (shouldn't make a difference). Should we able to create a read-only List implementation where only one of the handler instances exist in the engine ? -- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
