Hi all,
I currently have asp pages that clients submit xml transactions to. The asp pages take the xml and validate it against a schema. Some other light validation ocurrs and the data is fed into a SQL db. I've recently developed a web service which has the same functionality as the asp pages. I would now like to strip the guts out of the asp pages and just use them as a pass through layer to the web service.
I would like to implement this by creating a “gateway” in the form of a .NET COM object. Within the ASP page, a .NET COM object is instantiated (the “gateway”), and a method is called that passes the XML input to the COM layer. The COM layer takes the XML input, wraps the required SOAP header around the XML, and calls the appropriate web service function.
One might ask the question, “Why not access the Web Service Layer directly from the ASP layer”. The answer to that is portability. As far as I am aware, there are only 2 options for calling a web service from the ASP layer:
1. Use the MSXML 4 object to Get/Post data to the web service.
2. Use the SOAP COM object to interface with the web service.
Option 1 is problematic since one of my goals is to avoid using MSXML going forward. I have seen it behave unexpectedly or in an unstable manner from time to time so it is not considered a good long term solution.
Option 2 refers to the SOAP object with is problematic because Microsoft has declared the object deprecated so it is obviously not a good long term solution.
I would like your opinions on this solution as well as any good links that you may be able to provide for help. I've searched all over the net but am not having much luck. Acutally, I'm not even certain what I'm searching for at this point.
Thanks for the help
Trent
I currently have asp pages that clients submit xml transactions to. The asp pages take the xml and validate it against a schema. Some other light validation ocurrs and the data is fed into a SQL db. I've recently developed a web service which has the same functionality as the asp pages. I would now like to strip the guts out of the asp pages and just use them as a pass through layer to the web service.
I would like to implement this by creating a “gateway” in the form of a .NET COM object. Within the ASP page, a .NET COM object is instantiated (the “gateway”), and a method is called that passes the XML input to the COM layer. The COM layer takes the XML input, wraps the required SOAP header around the XML, and calls the appropriate web service function.
One might ask the question, “Why not access the Web Service Layer directly from the ASP layer”. The answer to that is portability. As far as I am aware, there are only 2 options for calling a web service from the ASP layer:
1. Use the MSXML 4 object to Get/Post data to the web service.
2. Use the SOAP COM object to interface with the web service.
Option 1 is problematic since one of my goals is to avoid using MSXML going forward. I have seen it behave unexpectedly or in an unstable manner from time to time so it is not considered a good long term solution.
Option 2 refers to the SOAP object with is problematic because Microsoft has declared the object deprecated so it is obviously not a good long term solution.
I would like your opinions on this solution as well as any good links that you may be able to provide for help. I've searched all over the net but am not having much luck. Acutally, I'm not even certain what I'm searching for at this point.
Thanks for the help
Trent
