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 / January 2007

Tip: Looking for answers? Try searching our database.

SOAP Toolkit client problems with DotNet Service

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Michael Russell - 12 Jan 2007 18:19 GMT
Hi all,
I'm trying to get a client working with my ASP.NET web service.  The
client's been working great up to this point with a SOAP
Toolkit-generated service based on a VB COM library.

On the client side, I'm calling the web service here:
Signature

Dim soapClient As SoapClient30
Dim xmlList As IXMLDOMNodeList

Set soapClient = GetSoapConnection
Set xmlList = soapClient.GetGroups(SYSTEM_NAME)
--
and at that last line, I get a "424 - Object required" error.

I haven't modified the code at all except to point to the new WSDL.

In the debugger I can see that "soapClient.GetGroups(SYSTEM_NAME)"
contains a list of Nodes, so it's calling the service and successfully
retrieving the message, but it refuses to process it.

Any guidance on this would be GREATLY appreciated.

Shailen Sukul - 15 Jan 2007 02:54 GMT
Sounds like the fully qualified name of your object has changed when you
repointed it.
try changing your proxy's business objects to the new namespace.

HTH.

Signature

With Regards
Shailen Sukul
.Net Architect
(MCPD: Ent Apps, MCSD.Net MCSD MCAD)
Ashlen Consulting Services
http://www.ashlen.net.au

> Hi all,
> I'm trying to get a client working with my ASP.NET web service.  The
> client's been working great up to this point with a SOAP Toolkit-generated
> service based on a VB COM library.
>
> On the client side, I'm calling the web service here:
Michael Russell - 17 Jan 2007 12:17 GMT
> Sounds like the fully qualified name of your object has changed when you
> repointed it.
> try changing your proxy's business objects to the new namespace.
>
> HTH.

Thanks for the feedback, but I'm not sure that's a problem, unless I'm
missing something else.  The only place I'm aware of that the STK object
in the VB project sees the namespace is from the dynamically-generated
WSDL of the service, in this code from the GetSoapConnection function:

--
    Dim sp As New SoapClient30
    Dim strPath As String

    strPath = ActiveWorkbook.Path

    With sp
        .MSSoapInit "http://localhost:1418/PigData/Service.asmx?WSDL", _
            "", "", ""
        .ConnectorProperty("EndPointURL") = _
            "http://localhost:1418/PigData/Service.asmx"
    End With

    Set GetSoapConnection = sp
--

Could it have something to do with the fact that I'm passing a
System.DateTime object and VB doesn't know what to do with it?

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.