«

I just want to check my facts.

I've heard some differing accounts, but my understanding of an article I
read on the MSDN site is, if you throw an exception in a web service, the
exception is encapsulated in a SoapException, returned as a Soap <fault> and
the SoapException is thrown on the client. Is my understanding of this
correct?

I just want to make sure if I'm throwing exceptions in the web service that
the client is going to get them. I seem to recall some postings where people
were saying exceptions they were throwing in their web services weren't
being thrown on the client, but instead were causing issues in their web
service itself (crashing?). I don't recall how those topics were resolved,
however.

Thanks

Pete davis

--
http://www.petedavis.net

Nope, if you throw them, they will be caught at the client as a
SOAPException. However, a preferred way would be to catch the exception on
the web service end, fill out the detail node of the SOAPException, and have
the client catch that with the detail so they can understand what went
wrong.

Alex

"Pete Davis" <> wrote in message
news: news.com...
> I just want to check my facts.
>
> I've heard some differing accounts, but my understanding of an article I
> read on the MSDN site is, if you throw an exception in a web service, the
> exception is encapsulated in a SoapException, returned as a Soap <fault>
and
> the SoapException is thrown on the client. Is my understanding of this
> correct?
>
> I just want to make sure if I'm throwing exceptions in the web service
that
> the client is going to get them. I seem to recall some postings where
people
> were saying exceptions they were throwing in their web services weren't
> being thrown on the client, but instead were causing issues in their web
> service itself (crashing?). I don't recall how those topics were resolved,
> however.
>
> Thanks
>
> Pete davis
>
> --
> http://www.petedavis.net
>
>

Okay, then I misunderstood that. I was under the impression that the
SoapException would have my exception as an InnerException. Thanks.

Pete
--
http://www.petedavis.net

"Trebek" <> wrote in message
news:40212ef9$0$82256$...
> Nope, if you throw them, they will be caught at the client as a
> SOAPException. However, a preferred way would be to catch the exception
on
> the web service end, fill out the detail node of the SOAPException, and
have
> the client catch that with the detail so they can understand what went
> wrong.
>
> Alex
>
> "Pete Davis" <> wrote in message
> news: news.com...
> > I just want to check my facts.
> >
> > I've heard some differing accounts, but my understanding of an article I
> > read on the MSDN site is, if you throw an exception in a web service,
the
> > exception is encapsulated in a SoapException, returned as a Soap <fault>
> and
> > the SoapException is thrown on the client. Is my understanding of this
> > correct?
> >
> > I just want to make sure if I'm throwing exceptions in the web service
> that
> > the client is going to get them. I seem to recall some postings where
> people
> > were saying exceptions they were throwing in their web services weren't
> > being thrown on the client, but instead were causing issues in their web
> > service itself (crashing?). I don't recall how those topics were
resolved,
> > however.
> >
> > Thanks
> >
> > Pete davis
> >
> > --
> > http://www.petedavis.net
> >
> >
>
>

Here's an article that shows how you can create some wrapper classes to make
life with SoapExceptions easier:
http://tinyurl.com/25j4q

--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan


"Pete Davis" <> wrote in message
news: news.com...
> Okay, then I misunderstood that. I was under the impression that the
> SoapException would have my exception as an InnerException. Thanks.
>
> Pete
> --
> http://www.petedavis.net
>
> "Trebek" <> wrote in message
> news:40212ef9$0$82256$...
> > Nope, if you throw them, they will be caught at the client as a
> > SOAPException. However, a preferred way would be to catch the exception
> on
> > the web service end, fill out the detail node of the SOAPException, and
> have
> > the client catch that with the detail so they can understand what went
> > wrong.
> >
> > Alex
> >
> > "Pete Davis" <> wrote in message
> > news: news.com...
> > > I just want to check my facts.
> > >
> > > I've heard some differing accounts, but my understanding of an article
I
> > > read on the MSDN site is, if you throw an exception in a web service,
> the
> > > exception is encapsulated in a SoapException, returned as a Soap
<fault>
> > and
> > > the SoapException is thrown on the client. Is my understanding of this
> > > correct?
> > >
> > > I just want to make sure if I'm throwing exceptions in the web service
> > that
> > > the client is going to get them. I seem to recall some postings where
> > people
> > > were saying exceptions they were throwing in their web services
weren't
> > > being thrown on the client, but instead were causing issues in their
web
> > > service itself (crashing?). I don't recall how those topics were
> resolved,
> > > however.
> > >
> > > Thanks
> > >
> > > Pete davis
> > >
> > > --
> > > http://www.petedavis.net
> > >
> > >
> >
> >
>
>