|
|
You're in the
dotnet web services
group:webservice & nhibernate
dotnet web services:
Hi all,
I'm trying to set up a .NET webservice using in data access layer Nhibernate (nhib 1.2.0 beta). The first trouble I met was that a webservice cannot serialize Interfaces, like IList<>. After I workarounded it, now I get: System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: CProxyType<<My_NamespaceNAme>><<MyclassName>>_NHibernate_ProxyINHibernateProxy_System_Runtime_SerializationISerializable2 cannot be serialized because it does not have a parameterless constructor. at System.Xml.Serialization.TypeDesc.CheckSupported() There is anyone out there using nhibernate for webservices?? Thanks. Regards gaddoz
Hi,
Using the NHibernate entities as messages for a web service is not a good approach. The client will only receive a xml copy of the entire entity graph, which sometimes can involve many tables. (It is not going to receive the entity itself). In addition, you will have the serialization problems that you mention. It is better to have a different class representing the web service message (A simple class decorated with XML serialization attributes) and an adapter layer that maps the message with the NHibernate entity. Regards, Pablo Cibraro. [quoted text, click to view] "gaddoz" <gaddozANTISPAM@ANTISPAMgmail.com> wrote in message news:45621fa4$0$19237$4fafbaef@reader4.news.tin.it... > Hi all, > > I'm trying to set up a .NET webservice using in data access layer > Nhibernate (nhib 1.2.0 beta). > The first trouble I met was that a webservice cannot serialize Interfaces, > like IList<>. > > After I workarounded it, now I get: > > System.InvalidOperationException: There was an error generating the XML > document. ---> System.InvalidOperationException: > CProxyType<<My_NamespaceNAme>><<MyclassName>>_NHibernate_ProxyINHibernateProxy_System_Runtime_SerializationISerializable2 > cannot be serialized because it does not have a parameterless constructor. > at System.Xml.Serialization.TypeDesc.CheckSupported() > > > There is anyone out there using nhibernate for webservices?? > > Thanks. > Regards > > gaddoz >
[quoted text, click to view]
"gaddoz" <gaddozANTISPAM@ANTISPAMgmail.com> wrote in message news:4563546c$0$3200$4fafbaef@reader2.news.tin.it... > Thanks for the reply Pablo. > > So, are you saying that in my pattern I should separate > "Model Objects" from "Nhibernate Objects"? > > I don't like this idea! > Now I'm using model objects, a data access layer that uses these objects > against Nhibernate and a business layer that calls the DAL. > > What do you suggest me? I suggest that you add a third class of object - Data Transfer Objects (DTO). You use a DTO to transfer data between the web
[quoted text, click to view]
"John Saunders" <john.saunders at trizetto.com> wrote in message news:eqJ2saaDHHA.3492@TK2MSFTNGP02.phx.gbl... > "gaddoz" <gaddozANTISPAM@ANTISPAMgmail.com> wrote in message > news:4563546c$0$3200$4fafbaef@reader2.news.tin.it... >> Thanks for the reply Pablo. >> >> So, are you saying that in my pattern I should separate >> "Model Objects" from "Nhibernate Objects"? >> >> I don't like this idea! >> Now I'm using model objects, a data access layer that uses these objects >> against Nhibernate and a business layer that calls the DAL. >> >> What do you suggest me? > > I suggest that you add a third class of object - Data Transfer Objects > (DTO). You use a DTO to transfer data between the web Sorry, got sent too soon. You use a DTO to transfer data between the web service and the client. It is an object which represents the data in a simple format whose only purpose is to transfer the data. There is no business logic and no database logic in these objects, just data. These will also map more closely to XML, and so will be more likely to be compatible between client and server. For instance, instead of using collections, the DTO will use arrays. This allows you to use whatever business-layer or data layer object you like inside of your server, yet to only present the data itself to the clients. John
Thanks for the reply Pablo.
So, are you saying that in my pattern I should separate "Model Objects" from "Nhibernate Objects"? I don't like this idea! Now I'm using model objects, a data access layer that uses these objects against Nhibernate and a business layer that calls the DAL. What do you suggest me? Regards Gaddoz Pablo Cibraro [MVP] ha scritto: [quoted text, click to view] > Hi,
> > Using the NHibernate entities as messages for a web service is not a good > approach. The client will only receive a xml copy of the entire entity > graph, which sometimes can involve many tables. (It is not going to receive > the entity itself). > In addition, you will have the serialization problems that you mention. It > is better to have a different class representing the web service message (A > simple class decorated with XML serialization attributes) and an adapter > layer that maps the message with the NHibernate entity. > > Regards, > Pablo Cibraro. > > "gaddoz" <gaddozANTISPAM@ANTISPAMgmail.com> wrote in message > news:45621fa4$0$19237$4fafbaef@reader4.news.tin.it... >> Hi all, >> >> I'm trying to set up a .NET webservice using in data access layer >> Nhibernate (nhib 1.2.0 beta). >> The first trouble I met was that a webservice cannot serialize Interfaces, >> like IList<>. >> >> After I workarounded it, now I get: >> >> System.InvalidOperationException: There was an error generating the XML >> document. ---> System.InvalidOperationException: >> CProxyType<<My_NamespaceNAme>><<MyclassName>>_NHibernate_ProxyINHibernateProxy_System_Runtime_SerializationISerializable2 >> cannot be serialized because it does not have a parameterless constructor. >> at System.Xml.Serialization.TypeDesc.CheckSupported() >> >> >> There is anyone out there using nhibernate for webservices?? >> >> Thanks. >> Regards >> >> gaddoz >> >
John Saunders ha scritto:
[quoted text, click to view] > "John Saunders" <john.saunders at trizetto.com> wrote in message > news:eqJ2saaDHHA.3492@TK2MSFTNGP02.phx.gbl... >> "gaddoz" <gaddozANTISPAM@ANTISPAMgmail.com> wrote in message >> news:4563546c$0$3200$4fafbaef@reader2.news.tin.it... >>> Thanks for the reply Pablo. >>> >>> So, are you saying that in my pattern I should separate >>> "Model Objects" from "Nhibernate Objects"? >>> >>> I don't like this idea! >>> Now I'm using model objects, a data access layer that uses these objects >>> against Nhibernate and a business layer that calls the DAL. >>> >>> What do you suggest me? >> I suggest that you add a third class of object - Data Transfer Objects >> (DTO). You use a DTO to transfer data between the web > > Sorry, got sent too soon. > > You use a DTO to transfer data between the web service and the client. It is > an object which represents the data in a simple format whose only purpose is > to transfer the data. There is no business logic and no database logic in > these objects, just data. > > These will also map more closely to XML, and so will be more likely to be > compatible between client and server. For instance, instead of using > collections, the DTO will use arrays. > > This allows you to use whatever business-layer or data layer object you like > inside of your server, yet to only present the data itself to the clients. > > John > > Many thanks guys. So, go on for DTO! Any suggestion for a fast way for moving data between model and dto? :)
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |