RE: Data types in Pattern & Practices Web Service Software Factory
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Thu, 14 Dec 2006 07:20:33 GMT
Hello Henrik,
I've also found your another thread regarding on a custom type with Generic
List member issue. I haven't noticed that you're using the "Service
factory", now I get it here. As for the "Service Factory", it by default
provide a recommend structure of webservice solution architecture and mapp
each abstract solution layer to certain visual studio projects in a
template solution. And you're surely able to customize them as your
specific scenario.
For your scenario here, if you think duplicate the same custom class in
both busicness and service contact layer, you can directly modify the
service contract and implemention layer and use those classes used in
business layer. However, make sure those classes are well defined for using
in ASP.NET webservice since they'll need to be serialized in XML soap
message. The reason why the "service factory" will create two set of such
classes in both service contact and business layers are that the classes
used in business layer may contains many fields/methods that are specific
to busines logic rather than data/properties. And webservice layer only
need some light weight classes which concentrate on the data it will hold.
#Web Service Software Factory
http://msdn.microsoft.com/msdnmag/issues/06/12/ServiceStation/Default.aspx?l
oc=en#S3
Hope this helps.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- Data types in Pattern & Practices Web Service Software Factory
- From: Henrik Skak Pedersen
- Data types in Pattern & Practices Web Service Software Factory
- Prev by Date: Re: HTTP status 401: Access Denied
- Next by Date: sending data to another server and receiving data as response
- Previous by thread: Data types in Pattern & Practices Web Service Software Factory
- Next by thread: MSSOAPLib30.SoapClient30 scalability problem
- Index(es):
Relevant Pages
|