No matter whether or not you think about SOA as implemented by SOAP, REST or messaging, services are document-centric. Services are not object-oriented.
While polymorphism is a strong design tool in OOD, it’s not applicable in SOA because SOA modeling doesn’t involve classes.
More Related Contents:
- Large WCF web service request failing with (400) HTTP Bad Request
- WCF Service Client: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding
- “Do not use Abstract Base class in Design; but in Modeling/Analysis”
- Returning DataTables in WCF/.NET
- Client configuration to consume WCF JSON web service
- Web Service without adding a reference?
- Performance Tests of Serializations used by WCF Bindings
- Understanding WCF Windows Authentication
- creating WCF ChannelFactory
- How to make a call to my WCF service asynchronous?
- How can I install a certificate into the local machine store programmatically using c#?
- IIS WCF service hosting vs Windows Service
- How to add parameters into a WebRequest?
- Different forms of the WCF service contract interface
- Why method overloading is not allowed in WCF?
- Caching in WCF?
- Can I have an optional parameter for an ASP.NET SOAP web service
- WCF – Design Parameter Decision
- CORS Support within WCF REST Services
- How to call wcf service Asynchronously
- Create web service proxy in Visual Studio from a WSDL file
- Error in WCF client consuming Axis 2 web service with WS-Security UsernameToken PasswordDigest authentication scheme
- Consume a SOAP web service without relying on the app.config
- How can I prevent BufferManager / PooledBufferManager in my WCF client app from wasting memory?
- My CustomAuthorizationPolicy.Evaluate() method never fires
- Service Reference Error: Failed to generate code for the service reference
- Passing Interface in a WCF Service?
- Signing SOAP messages using X.509 certificate from WCF service to Java webservice
- Is TLS 1.1 and TLS 1.2 enabled by default for .NET 4.5 and .NET 4.5.1?
- The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)