ashvini Posted February 19, 2007 Share Posted February 19, 2007 <definitions name="HelloService" targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema">these are the usual line of any WSDL file- can anybody tell why we use the lines- xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema"I didn't find even in w3c school tutorial. can anybody help in to find the reason why we ware using these- line by line can anybody tell what the significance of using these line-Please Before ans read This- don't repeat this answer- I got ans in many tutorial like this- The use of namespaces is important for differentiating elements, and it enables the document to reference multiple external specifications, including the WSDL specification, the SOAP specification, and the XML Schema specification.So - My question is what kind of differentiate example ?? What do you mean by multiple external specification - while WSDL have single one standard format ?? What exactly this specification does, is there any sense to use them ??Can any body - Link to comment Share on other sites More sharing options...
boen_robot Posted March 3, 2007 Share Posted March 3, 2007 As you should've already understood, those are namespace references. Namespaces allow you to "embed" one XML based language into another. For example, having the SOAP namespace means you can embed SOAP in the WSDL document.By "external specification" people mean "a specification other then the main one" which in this case is SOAP (while the main specification is WSDL), but can also be any other, including non-W3C ones, such as the tns namespace.Having that said, what exactly does which specification do?Another example you say... here's a sample XSLT file which has the XSLT and the XHTML namespace: <?xml version="1.0" encoding="ISO-8859-1"?><xsl:stylesheet version="1.0"xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml"><xsl:template match="/"> <html> <body> <h2>My CD Collection</h2> <table border="1"> <tr bgcolor="#9acd32"> <th>Title</th> <th>Artist</th> </tr> <xsl:for-each select="catalog/cd"> <tr> <td><xsl:value-of select="title"/></td> <td><xsl:value-of select="artist"/></td> </tr> </xsl:for-each> </table> </body> </html></xsl:template></xsl:stylesheet> In this example, the XSL prefix is used to tell the XSLT processor (the application using the file) that those elements with that prefix are what the application needs to process. All non-prefixed elements are part of the XHTML specification and the application that is going to render this output is going to have this in mind. Link to comment Share on other sites More sharing options...
ashvini Posted March 5, 2007 Author Share Posted March 5, 2007 Thanx.... Boen... Thanks a lot..Regards,Ashvini Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now