• Post Reply Bookmark Topic Watch Topic
  • New Topic

targetnamespace

 
Tina Shupe
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I know that this may seem as a weird question but I cant' find anything that proves what I am thinking.
I have a WSDL that has
<definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://intranet.bts.wrbc/DWServices/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://home.find/Services/" xmlns="http://schemas.xmlsoap.org/wsdl/">
And when I copy the targetNamespace into internet explorer like the rest I get a page not found. Am I wrong in thinking that this could be a major problem, and that the page should be found. This targetNamespace also carries over into the Soap

I was just wondering if it appears that I could have issues with the targetNamespace not resolving, or is it of little importance.
Thanks
[ February 13, 2003: Message edited by: Tena Shupe ]
 
Rich Raposa
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The use of URLs as a namespace is to be (somewhat) assured of a unique namespace. However, they do not have to resolve to an actual URL, so I'm not surprised you got a "page not found" response.
 
Tina Shupe
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
so in short my SOAP call should still work even through the targetNamespace can not be resolved.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!