Why do you want to do that? Domain objects are not suited to be sent over wire, they are to fine grained. Remember Fowler's first law of object distribution: do not distribute. Further, using domain objects in your remoting services introduces coupling between services, sensitivity to domain model refactorings/redesigns (which are frequent by nature) and it introduces serious versioning problems.
My advice would be to use some form of DTO, that is mapped in the service layer to shield remoting and domain model. That way you can protect both. This is an approach typically used withing SOA and distribution szenarios. Remind not to reuse DTOs among services. -Sebastian N.D. schrieb: > hey all, anyone has such experience or can reference to resources? > I understand there are some properties that needs to be attached to the > entity in order to make serialization with WCF happen, and that > serializing to XML > is one solution > > thanks > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
begin:vcard fn:Sebastian Jancke n:Jancke;Sebastian email;internet:[EMAIL PROTECTED] version:2.1 end:vcard
