I'm using lots of defaults/provided features. I don't actually see any
"soap" headers, but I turned off Soap12 and issued requests from test client
using both Soap11 and Soap12 and Soap11 worked and Soap12 failed - couldn't
parse it.
Custom classes built from XSD. Early binding seems to be behaving fine on
both WS and Client sides using these objects.
When I run WS locally (invoked from within instance of IDE) and then invoke
Test Client (invoked from within second instance of IDE) this all works.
When running on IIS server, I can bring up WS to get the default
ServiceDescription page. Looks okay.
When I invoke Test aspx page on server it gets error back. I create an
instance of the Request object and prior to invoking WS I save request to XML
file and it looks fine.
I will try to answer your questions:
** Your webservice's code logic(such as soap message schema)
<WebMethod(Description:="Returns one or more deposit rates based
upon request values", EnableSession:=False)> _
Public Function getRates(ByVal Request As RequestObject.RATEDOC) As
ResponseObject.RATEDOC
sUser = Me.User.Identity.Name ' This is empty when run from test server
If Me.User.Identity.IsAuthenticated Then ' this is false when run from
test server
.
(code)
.
End If
Return RateDOC
End Function ' getRates
** your webservice's deployment scenario(security ...)
So far just Windows authentication.
** How to consume the webservice through remote client and any different
from the approach you visit it locally
Same test aspx page. I also rebuilt all components on Test server from the
IDE on the server, and rebult WSDL, then modified test aspx page to use
updated WSDL.
[quoted text, click to view] "Steven Cheng[MSFT]" wrote:
> Hi Doug,
>
> From your description, you have an ASP.NET based webservice that will
> accept and return some custom defined class objects(follow your own xml
> schema), the webservice can be consumed correctly locally, but fail when
> accessing remotely, correct?
>
> As for the "UserId or isAuthenticated" is it any IIS or ASP.NET specific
> authentication or your own custom authentication in the webservice request
> schema definition? So far I'm still not very clear about your webservice's
> detailed code logic and deployment scenario. Would you provide some further
> info on this?
>
> ** Your webservice's code logic(such as soap message schema)
> ** your webservice's deployment scenario(security ...)
> ** How to consume the webservice through remote client and any different
> from the approach you visit it locally
>
> Also, please feel free to let me know if there is anything I misunderstand.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
>
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
>
http://msdn.microsoft.com/subscriptions/support/default.aspx. >
> ==================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>
>
>
>
>
>
>