Back!
so it has been a very very long while since i put anything on this blog, but well things has been quite crazy :)
anyway, lately i have been doing alot of investment in WCF/WSE. things with regards to specs and definitly deep dive in WCF.
i have been always one of those guys who had lots of problems with [WebMethod] framework. simply the fact that you don't create your interface sepratly as in you define it somewhere then consume or implement in fact you design & implement your prog interface by tagging methods on a class with [WebMethod] !
additionally (just a little example) you have no control over WSDL which is quite a shame cause there is alot of intersting stuff to be done on this front
anyway the 2 combined factors created a mess of web services. with badly designed WSDL & web services in general
got to admin: WSE team is the first from microsoft side to acknowlege the defect and fixed it in thier own implementation led by smart people like Yasser Shohod. and it is simple you create interface following
[WebServiceBinding( Name = "StockService", Namespace = "http://stockservice.contoso.com/wse/samples", ConformsTo = WsiProfiles.BasicProfile1_1, EmitConformanceClaims = true)]
interface IStockService
{
//Operation goes here
}
then you create your service implementation
[WebService( Namespace = "http://stockservice.contoso.com/wse/samples")] public class StockService : IStockService
{
//SERVICE HERE
}
that was primarly aiming towards implementing services outside IIS scope.
later on WCF took this further by using servicecontract terminilogy (very smart choice) and definitly instance managment.
more on this on later posts
anyway, lately i have been doing alot of investment in WCF/WSE. things with regards to specs and definitly deep dive in WCF.
i have been always one of those guys who had lots of problems with [WebMethod] framework. simply the fact that you don't create your interface sepratly as in you define it somewhere then consume or implement in fact you design & implement your prog interface by tagging methods on a class with [WebMethod] !
additionally (just a little example) you have no control over WSDL which is quite a shame cause there is alot of intersting stuff to be done on this front
anyway the 2 combined factors created a mess of web services. with badly designed WSDL & web services in general
got to admin: WSE team is the first from microsoft side to acknowlege the defect and fixed it in thier own implementation led by smart people like Yasser Shohod. and it is simple you create interface following
[WebServiceBinding( Name = "StockService", Namespace = "http://stockservice.contoso.com/wse/samples", ConformsTo = WsiProfiles.BasicProfile1_1, EmitConformanceClaims = true)]
interface IStockService
{
//Operation goes here
}
then you create your service implementation
[WebService( Namespace = "http://stockservice.contoso.com/wse/samples")] public class StockService : IStockService
{
//SERVICE HERE
}
that was primarly aiming towards implementing services outside IIS scope.
later on WCF took this further by using servicecontract terminilogy (very smart choice) and definitly instance managment.
more on this on later posts
