I've seen this question before and the answer, but I couldn't find it
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.
HTH,
Sam
----------------------------------------------
Blog: http://www.rewindlife.com
Chart: http://www.blinex.com/products/charting
----------------------------------------------
-----Original Message-----
From: Dave Carabetta [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 2:29 PM
To: CF-Talk
Subject: MX 6.1 and MapPoint
(Searching the archives, it doesn't sound like anybody has, but I'm not sure
if people have figured it out in the interim and just never posted)
Has anybody been able to get MX 6.1 to successfully connect with the
Microsoft MapPoint 3.0 web service? Apache throws up on it, and searching
the MS forums suggests that the Axis 1.1 engine can't successfully integrate
with the service. Any pointers? I'm pretty new to web services, and
references to wsdl2java and java2wsdl are a little over my head at this
point.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
