Hi, I've been bashing my head against the wall trying to figure this out...it's not as helpful as reading the documentation, but it hurts just as much <g>.
I'm successfully using an Axis 1.1 client to talk to a .NET service. The WSDL2Java tool worked well for the most part, but there were one or two tweaks I had to make as Axis doesn't yet appear to support the <list> type that M$ loves so much. My remaining stumbling block appears to be with sending the SOAP Headers the way .NET wants to get them. (The SOAP Body is perfect.) I've successfully been using the setHeader method of the Stub to add new headers, however, Axis keeps adding xsi:type attributes, despite the fact that I've got: _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, Boolean.FALSE); (Does this setting not apply to headers added via the Stub? I did try adding a header via _call.addHeader, but that didn't seem to do the trick either.) So, instead of getting: <soapenv:Header> <UserInfoRouteHeader xmlns="http://s.mappoint.net/mappoint-30/"> <DefaultDistanceUnit>Mile</DefaultDistanceUnit> </UserInfoRouteHeader> </soapenv:Header> I get: <soapenv:Header> <ns1:UserInfoRouteHeader soapenv:mustUnderstand="0" xsi:type="ns1:UserInfoRouteHeader" xmlns:ns1="http://s.mappoint.net/mappoint-30/"> <DefaultDistanceUnit>Mile</DefaultDistanceUnit> </ns1:UserInfoRouteHeader> </soapenv:Header> Here's how I'm adding the header: UserInfoRouteHeader userInfo = new UserInfoRouteHeader () ; userInfo.setDefaultDistanceUnit (DistanceUnit.Mile) ; setHeader ("http://s.mappoint.net/mappoint-30/", "UserInfoRouteHeader", userInfo) ; Can anyone point me in the right direction? Thanks. -Chris