Hi WS Developers,
I have am working on an integration project in which we are using WSDL and
MS XML WebServices to integrate legacy systems other with external systems.
Unfortunately, we must use the SessionState provider (ASP.NET 2.0) to allow
webservices to expose the statefull architecture of the legacy systems.
Within the WSDL test page, everything works perfectly. I can make
sequential WebService calls and the state of the previous call is retained as
expected. However, this doesn't work when being called outside of the
automatically generated WSDL document (i.e inside an ASP.NET application).
I have tried quite a few StateProviders and configurations and nothing seems
to make a difference. I added some debugging and noticed that the
Context.Session .SessionID is being reset for every request from an ASP.NET
page (even if it is from a button on the same page). When testing from the
WSDL test invoke page, the Context.Session .SessionID remained the same
between subsequent calls and the SessionState was correctly restored.
This appears to occur with VS.NET 2005 Pro on Windows 2000 as well as VS.NET
2005 Express on Win2003 SP1. I am all out of ideas and any help would be
greatly appreciated.
Thanks,
--
Fabian Anderson
Systems Analyst / Programmer
I have am working on an integration project in which we are using WSDL and
MS XML WebServices to integrate legacy systems other with external systems.
Unfortunately, we must use the SessionState provider (ASP.NET 2.0) to allow
webservices to expose the statefull architecture of the legacy systems.
Within the WSDL test page, everything works perfectly. I can make
sequential WebService calls and the state of the previous call is retained as
expected. However, this doesn't work when being called outside of the
automatically generated WSDL document (i.e inside an ASP.NET application).
I have tried quite a few StateProviders and configurations and nothing seems
to make a difference. I added some debugging and noticed that the
Context.Session .SessionID is being reset for every request from an ASP.NET
page (even if it is from a button on the same page). When testing from the
WSDL test invoke page, the Context.Session .SessionID remained the same
between subsequent calls and the SessionState was correctly restored.
This appears to occur with VS.NET 2005 Pro on Windows 2000 as well as VS.NET
2005 Express on Win2003 SP1. I am all out of ideas and any help would be
greatly appreciated.
Thanks,
--
Fabian Anderson
Systems Analyst / Programmer