Absolutely Deepal. I was suggesting that we should use the same pattern we have already set.
thanks, dims On 9/18/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi dims; This is what we have right now , I mean one can implement Service interface or just have session related method in the service impl class. - if he has implement the interface , then we check the instance of the service impl class , then call method accordingly - else we check to see whether those method are there in the service impl class , and if there are there we call them using java reflection. So I am +1 to have that. > Sanjiva, > > How about this? We define the interface, If people want to use it, > they can. But our code will be smart enough to reflectively look for > the method+parameters and call it even if the class does not implement > the interface. An interface is good for documenting the capabilities > in a easy to understand form for our users. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
