>anywhere. Here's what I can remember.
>
>The problem is that the MapPoint WSDL defines multiple services. While
>this
>is a perfectly valid thing to do, AXIS doesn't support multiple service
>definitions in a single WSDL. The work-around is to create a local WSDL
>file that has all the necessary info from just a part of the official WSDL
>for the service you need. Then just point your code to your local WSDL and
>it reportedly works. Remember the WSDL contains the soap address for the
>actual server, so even with a local WSDL it can use a remote server for the
>actual invocation.
Thanks for the info. I had actually seen that tip before, and somebody
mentioned splitting the WSDL file out into single service WSDL files, but
because I can't figure out what one service needs from the master document,
I don't know where to split the file up. Oh well, my co-worker's whipping
something up in Python, so we'll probably use that. I was just hoping to be
able to use MX/Java to get it done.
Thanks again,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
