Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / December 2005

Tip: Looking for answers? Try searching our database.

Debugging Inherited Methods in SoapReceiver

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
irwin.williams - 05 Dec 2005 14:47 GMT
Hello
I am working on a project where i need to trace the flow of operations
through a class i am using for my web services.
This class inherits from SoapService (which inherits from
SoapReceiver).
I have sought to separate my test programme from the library with uses
SoapService (lets call it MySoapLibrary). However, when i seek to debug
MySoapLibrary, none of the debug commands i apply to my methods are
called, even though i know  - though implicitly - that these methods
must be called.
For example, lets say i have a class called MathService : SoapService.
I have overridden a method called processmessage(), but i am not
"seeing it" being called.
public class MathService : SoapService{
    public override void ProcessMessage(SoapEnvelope message)
        {
            Console.WriteLine("in pm");
            base.ProcessMessage(message);
        }
}
I have even put some Console.WriteLine statements in some of my
inherited methods, as shown above, but not even these messages are
printing.
Can someone show me where i am going wrong?
Thanks
irwin.williams - 05 Dec 2005 19:34 GMT
K, i figured out what i was doing wrong.
I was using a custom transport to handle the http communication for my
web service. (Aaron Skonnard's tutorial actually:
http://pluralsight.com/blogs/aaron/archive/2005/10/14/15571.aspx).
Part of the usage of it was to let my custom Service be wrapped in a
class called WsdlEnabledReceiver - which extended WebServiceReceiver.

I had intended for my Service to inherit from SoapService and use its
methods, however, by wrapping it in the WsdlEnabledReceiver the methods
i expected to be overriding were actually being used via the
WebServiceReceiver class - which is from a separate inheritance
heirarchy to SoapService and SoapReceiver.

This i removed the wrapping and was able to see my debugging
information.

Irwin.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.