robbo_b
01-30-2005, 11:38 PM
Hi,
I've worked on several projects now where we have used ASP.NET web services. One of the things I dislike is the need for a seperate .asmx file that contains the reference to the our web service implementation on the server and the lack of any hook that gives us some control over the instantiation and mapping of uris to web service implementations.
I was digging around trying to see wether or it would be possible to create a customised WebServiceHandlerFactory that instead of looking up the type from a .asmx file, did a lookup from a spring object factory based on the request uri, and then used the microsoft classes todo the rest of the soap serialisation/deserialisation. I would then map this handler factory to one of my own extensions i.e .sws
However, it appears all the microsoft classes needed to do all the normal soap processing are only visible to classes inside the System.Web.Services assembly, so that means my only other option is to implement all the soap stuff myself. It turns out the guys working on the mono project have finished porting asp.net web services stuff, so with their code, and a few minor modifications I was able to have my spring managed components exposed as web services, mapped to the *.sws extension.
I thought I'd mention this as I curious to see if anyway else knows of any other way to ave spring components exposed as web services.
rob
I've worked on several projects now where we have used ASP.NET web services. One of the things I dislike is the need for a seperate .asmx file that contains the reference to the our web service implementation on the server and the lack of any hook that gives us some control over the instantiation and mapping of uris to web service implementations.
I was digging around trying to see wether or it would be possible to create a customised WebServiceHandlerFactory that instead of looking up the type from a .asmx file, did a lookup from a spring object factory based on the request uri, and then used the microsoft classes todo the rest of the soap serialisation/deserialisation. I would then map this handler factory to one of my own extensions i.e .sws
However, it appears all the microsoft classes needed to do all the normal soap processing are only visible to classes inside the System.Web.Services assembly, so that means my only other option is to implement all the soap stuff myself. It turns out the guys working on the mono project have finished porting asp.net web services stuff, so with their code, and a few minor modifications I was able to have my spring managed components exposed as web services, mapped to the *.sws extension.
I thought I'd mention this as I curious to see if anyway else knows of any other way to ave spring components exposed as web services.
rob