Hi Rodrigu, Rodrigo Ruiz wrote: > > Eran Chinthaka wrote: >> We didn't want to put any restriction on a user who wanna write a simple >> java class and expose that as a web service. Thats been the case so far. >> I hope you can understand that it will make the most common and simple >> case simple. >> And I don't see a single reason behind the service impl being dependent >> on the web services engine being used. So thats why we didn't wanna >> define a contract for the service implementor to implement. > > Sorry Chintaka, but I think I miss something here. Why does implementing > an Axis2 interface makes your service more implementation dependent than > adding a method that receives an Axis2 parameter? > > Once you need to pass an OperationContext instance you are > implementation dependent, aren't you?.
Yes, that will happen iff you, as the service author, wanna get some information from the Axis2 environment. But, if you wanna deploy a simple service which does an xslt transformation on the recd xml, you don't wanna know what is happening in Axis2. Isn't it? -- Chinthaka
signature.asc
Description: OpenPGP digital signature
