[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
09/02/2009 at 09:43PM PDT, ID: 24703594
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
8.2

The prefix "wsdl" for element "wsdl:definitions" is not bound

Asked by ank9 in Web Services Description Language, Web Services, Extensible Markup Language (XML)

While parsing my WSDL I am getting the following error

    The prefix "wsdl" for element "wsdl:definitions" is not bound


Can someone please let me know the reason for the same.

Thank you 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3-b02-. -->
<wsdl:definitions name="TemplateService"
    targetNamespace="http://ws.impl.samples.services.dms.db.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://ws.impl.samples.services.dms.db.com/" 
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
    xmlns:ns="http://db.com/cobs/bpms/CaseService.xsd"  >  
    
    
    
    
    
    <wsdl:types>
        <xsd:schema>
            <xsd:import namespace="http://ws.impl.samples.services.dms.db.com/" 
                        schemaLocation="TemplateService_schema1.xsd"/>
        </xsd:schema>
        <xsd:schema>
            <xsd:import namespace="http://rt.fs.documentum.emc.com/" 
                        schemaLocation="TemplateService_schema2.xsd"/>
        </xsd:schema>
        <xsd:schema>
            <xsd:import namespace="http://impl.samples.services.dms.db.com/" 
                        schemaLocation="TemplateService_schema3.xsd"/>
        </xsd:schema>
        <xsd:schema>
            <xsd:import namespace="http://common.samples.services.dms.db.com/" 
                        schemaLocation="TemplateService_schema4.xsd"/>
        </xsd:schema>
        
        <!--  for BW -->
        <xsd:schema>
            <xsd:import namespace="http://db.com/cobs/bpms/Common.xsd" schemaLocation="Common.xsd"/>
        </xsd:schema>
        <xsd:schema>
            <xsd:import namespace="http://db.com/cobs/bpms/CaseService.xsd" schemaLocation="CaseService.xsd"/>
        </xsd:schema>
        <!--  BW ends-->
        
    </wsdl:types>
    
    <message name="getTemplateVersions">
        <part element="tns:getTemplateVersions" name="parameters"/>
    </message>
    <message name="getTemplateVersionsResponse">
        <part element="tns:getTemplateVersionsResponse" name="parameters"/>
    </message>
    <message name="ServiceException">
        <part element="ns1:ServiceException" name="fault" xmlns:ns1="http://rt.fs.documentum.emc.com/"/>
    </message>
    
    <!-- start BW -->
    <message name="Fault">
        <part element="ns1:FaultMessage" name="Fault"/>
    </message>
    <message name="RequestHeader">
        <part element="ns1:RequestHeader" name="RequestHeader"/>
    </message>
    <message name="ResponseHeader">
        <part element="ns1:ResponseHeader" name="ResponseHeader"/>
    </message>
    <message name="startCaseRequest">
        <part element="ns:CaseStartRequest" name="startCaseRequest"/>
    </message>
    <message name="startCaseResponse">
        <part element="ns:CaseStartResponse" name="startCaseResponse"/>
    </message>
    <!-- end BW -->
    
    <wsdl:portType name="TemplateServicePort">
        <operation name="getTemplateVersions">
            <input message="tns:getTemplateVersions"/>
            <output message="tns:getTemplateVersionsResponse"/>
            <fault message="tns:ServiceException" name="ServiceException"/>
        </operation>
    </wsdl:portType>
    <wsdl:binding name="TemplateServicePortBinding" type="tns:TemplateServicePort">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="getTemplateVersions">
            <soap:operation soapAction=""/>
            <wsdl:input>
                <soap:body use="literal"/>
                <soap:header message="tns:RequestHeader" part="RequestHeader" use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
                <soap:header message="tns:ResponseHeader" part="ResponseHeader" use="literal"/>
            </wsdl:output>
            <wsdl:fault name="ServiceException">
                <soap:fault name="ServiceException" use="literal"/>
            </wsdl:fault>
            
            
        </wsdl:operation>
        <!-- BW starts -->
        <wsdl:operation name="setCaseData">
            <soap:operation soapAction="/SharedResources/ServiceInterfaces/CaseService.serviceagent/CaseEndpoint1/setCaseData" style="document"/>
            <<wsdl:input>
                <soap:body parts="startCaseRequest" use="literal"/>
                <soap:header message="tns:RequestHeader" part="RequestHeader" use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body parts="startCaseResponse" use="literal"/>
                <soap:header message="tns:ResponseHeader" part="ResponseHeader" use="literal"/>
            </wsdl:output>
            <wsdl:fault name="fault">
                <soap:fault name="fault" use="literal"/>
            </wsdl:fault>
        </wsdl:operation>
        <!-- BW ends -->
        
    </wsdl:binding>
    <service name="TemplateService">
        <port binding="tns:TemplateServicePortBinding" name="TemplateServicePort">
            <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
        </port>
    </service>
</wsdl:definitions>
[+][-]09/02/09 11:11 PM, ID: 25248198

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Web Services Description Language, Web Services, Extensible Markup Language (XML)
Sign Up Now!
Solution Provided By: Gertone
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09/02/09 11:14 PM, ID: 25248208

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]09/03/09 12:03 AM, ID: 25248364

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20090824-EE-VQP-74 - Hierarchy / EE_QW_3_20080625