Hi Brett,
Take a look at the Fault.toString() method. It shows how to access
everything (actually, you can use it to print everything instead of as an
example).
Also, if you run the TcpTunnelGui tool, you can see what the other Fault
entries are.
Thanks,
-Matt
> -----Original Message-----
> From: Hansen, Richard [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 9:38 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Handling Faults
>
>
> "Unable to resolve target" normally means the service class can not be
> found. Normally, the class name would follow. I got "null" when my service
> class was found but could not be constructed.
>
> Rick Hansen
>
> > -----Original Message-----
> > From: Brett McLaughlin [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, July 04, 2001 5:25 PM
> > To: [EMAIL PROTECTED]
> > Subject: Handling Faults
> >
> >
> > I am getting an "Unable to resolve target: null" error, and
> > saw that the
> > troubleshooter said there was an element in the Fault to look
> > at for the
> > stack trace. However, none of the samples seem to show how to
> > do anything
> > but getting the fault error code and message. Any short snippets of
> > accessing the XML of the Fault as a DOM or whatever would
> > really help...
> >
> > -Brett
> >
>
