Interfaces And Web Services

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Joe - 03 Oct 2003 18:41 GMT

Hi,

Im having a little trouble with the fiollowing in a web service

Public Interface IBookAttribute
Property Description() As String
End Interface

I get "Cannot serialize Inteface MyApp.IBookAttribute"

Is it possible to do so, or are interfaces not a good idea for web services
(why not?)?

Thanks
Joe

Reply to this Message

Michael Pearson - 03 Oct 2003 22:01 GMT

I think it's because you don't impliment ISerializable. The webservice
doesn't know how to "translaste" your interface into XML. Do some research
on ISerializable and webservices.

Michael

> Hi,
>
[quoted text clipped - 11 lines]
> Thanks
> Joe

Reply to this Message

Simon Smith - 04 Oct 2003 10:26 GMT

On Fri, 3 Oct 2003 13:41:56 -0400 in article
<#0#FrWdiDHA.3104@tk2msftngp13.phx.gbl> in
microsoft.public.dotnet.framework.aspnet.webservices , "Joe"
<x@hotmail.com> wrote:

>Hi,
>
[quoted text clipped - 11 lines]
>Thanks
>Joe

I think that interfaces are almost by definition not serialisable. To
be serialisable a class must provide a default constructor - one with
no parameters: interfaces don't have and can't have constructors.

Signature

Simon
simon dot smith at snowvalley dot com
"Insomnia is a small price to pay for the stuff you read on UseNet"

Reply to this Message

Eirik M. - 05 Oct 2003 20:11 GMT

Search MSDN for an article about how to use interfaces and web-services.
Haven't got the link handy, but the articles is out there somewhere :-)

Eirik M

> On Fri, 3 Oct 2003 13:41:56 -0400 in article
> <#0#FrWdiDHA.3104@tk2msftngp13.phx.gbl> in
[quoted text clipped - 20 lines]
> be serialisable a class must provide a default constructor - one with
> no parameters: interfaces don't have and can't have constructors.

Reply to this Message

Joe - 06 Oct 2003 14:03 GMT

Thanks to all.
Joe

Reply to this Message

Interfaces And Web Services

Free Magazines