ws-woden-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jkapu...@apache.org
Subject svn commit: r546555 [1/2] - in /incubator/woden/trunk/java/ant-test: documents-bad-report.xml documents-good-report.xml test-suite-results.zip validation-results-without-ids.xml validation-results.xml
Date Tue, 12 Jun 2007 16:20:20 GMT
Author: jkaputin
Date: Tue Jun 12 09:20:19 2007
New Revision: 546555

URL: http://svn.apache.org/viewvc?view=rev&rev=546555
Log:
WODEN-149 
latest results after renumbering to the PR 
assertion numbers.

Modified:
    incubator/woden/trunk/java/ant-test/documents-bad-report.xml
    incubator/woden/trunk/java/ant-test/documents-good-report.xml
    incubator/woden/trunk/java/ant-test/test-suite-results.zip
    incubator/woden/trunk/java/ant-test/validation-results-without-ids.xml
    incubator/woden/trunk/java/ant-test/validation-results.xml

Modified: incubator/woden/trunk/java/ant-test/documents-bad-report.xml
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/ant-test/documents-bad-report.xml?view=diff&rev=546555&r1=546554&r2=546555
==============================================================================
--- incubator/woden/trunk/java/ant-test/documents-bad-report.xml (original)
+++ incubator/woden/trunk/java/ant-test/documents-bad-report.xml Tue Jun 12 09:20:19 2007
@@ -8,7 +8,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -20,7 +20,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFault-0058</key>
+      <key>BindingFault-1050</key>
       <message>The interface fault specified for this binding fault has already been specified on another binding fault. Each binding fault within a binding must specify a unique interface fault.</message>
     </error>
   </wsdl>
@@ -32,7 +32,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0057</key>
+      <key>Binding-1049</key>
       <message>A binding with the name &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoServiceBinding&apos; has already been defined for the description component. All bindings defined in the description component must have unique names.</message>
     </error>
     <error>
@@ -40,7 +40,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -48,7 +48,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -60,7 +60,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -72,7 +72,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -84,7 +84,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -96,7 +96,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0056</key>
+      <key>Binding-1048</key>
       <message>The type &apos;wsdl/http&apos; specified for this binding is not an absolute IRI. The type must be absolute.</message>
     </error>
   </wsdl>
@@ -108,7 +108,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFault-0058</key>
+      <key>BindingFault-1050</key>
       <message>The interface fault specified for this binding fault has already been specified on another binding fault. Each binding fault within a binding must specify a unique interface fault.</message>
     </error>
   </wsdl>
@@ -120,7 +120,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
     <error>
@@ -128,7 +128,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -140,7 +140,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
     <error>
@@ -148,7 +148,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -160,7 +160,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -172,7 +172,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingMessageReference-0060</key>
+      <key>BindingMessageReference-1052</key>
       <message>A binding message reference has already been specified for the interface message reference &apos;In&apos;. Each binding message reference within a binding operation component must specify a unique interface message reference.</message>
     </error>
   </wsdl>
@@ -184,7 +184,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingMessageReference-0060</key>
+      <key>BindingMessageReference-1052</key>
       <message>A binding message reference has already been specified for the interface message reference &apos;In&apos;. Each binding message reference within a binding operation component must specify a unique interface message reference.</message>
     </error>
   </wsdl>
@@ -196,8 +196,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1044</key>
+      <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -208,21 +208,13 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1044</key>
+      <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chameleon-1B/getBalance.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/customer/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chameleon-2B/getBalance.wsdl</uri>
@@ -235,22 +227,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/customer/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/account/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chat-1B/Chat-NoBindingInterface.wsdl</uri>
@@ -260,7 +236,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -272,7 +248,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;chatSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/chat.wsdl}say&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -288,7 +264,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Description-0025</key>
+      <key>Description-1006</key>
       <message>The target namespace &apos;example.org/Description&apos; is not an absolute IRI. The target namespace must be an absolute IRI.</message>
     </error>
   </wsdl>
@@ -300,7 +276,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>InterfaceMessageReference-0042</key>
+      <key>InterfaceMessageReference-1029</key>
       <message>An interface message reference with the message label &apos;Out&apos; has already been defined. An interface message reference must have a unique message label within the interface operation that contains it.</message>
     </error>
   </wsdl>
@@ -312,7 +288,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -410,23 +386,7 @@
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-1B/XSDImport.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-2B/XSDImportInWSDL.wsdl</uri>
@@ -439,42 +399,10 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-3B/XSDImport2.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-3B/XSDImportValid.wsdl</uri>
@@ -515,22 +443,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/EchoImpl&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/EchoImpl&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-8B/Echo.wsdl</uri>
@@ -559,22 +471,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Echo&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Echo&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Interface-1B/Interface.wsdl</uri>
@@ -584,7 +480,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0031</key>
+      <key>Interface-1012</key>
       <message>The styleDefault attribute contains the IRI &apos;wsdl/style/iri&apos;, which is not absolute. All IRIs specified for styleDefault must be absolute.</message>
     </error>
   </wsdl>
@@ -596,7 +492,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
   </wsdl>
@@ -608,7 +504,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface2&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
     <error>
@@ -616,7 +512,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
   </wsdl>
@@ -640,7 +536,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -660,15 +556,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -680,41 +568,17 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-1B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-2B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-3B/InterfaceMessageReference.wsdl</uri>
@@ -724,21 +588,13 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>InterfaceMessageReference-0042</key>
+      <key>InterfaceMessageReference-1029</key>
       <message>An interface message reference with the message label &apos;myLabel&apos; has already been defined. An interface message reference must have a unique message label within the interface operation that contains it.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-4B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceOperation-1B/echo-extended.wsdl</uri>
@@ -748,16 +604,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://www.wso2.com/schemas/2006/interop/EchoService&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://www.wso2.com/schemas/2006/interop/EchoService&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1045</key>
+      <message>The binding &apos;echoServiceSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echo&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -772,7 +620,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>MEP-0037</key>
+      <key>MEP-1022</key>
       <message>The message exchange pattern &apos;wsdl/in-out&apos; is not absolute. A message exchange pattern must be identified by an absolute IRI.</message>
     </error>
   </wsdl>
@@ -808,7 +656,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -820,7 +668,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -832,7 +680,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -844,7 +692,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -1015,7 +863,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0017</key>
+      <key>Schema-1069</key>
       <message>The XML schema imported from &apos;Schema.xsd&apos; must specify a target namespace.</message>
     </error>
     <error>
@@ -1023,7 +871,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/schema/&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -1035,69 +883,21 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/schema/&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-3B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-4B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-5B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-5B/SchemaContainer.wsdl</uri>
@@ -1111,7 +911,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0018</key>
+      <key>Schema-1073</key>
       <message>The element &apos;{http://example.org}element&apos; has already been defined in another inline XML Schema with the target namespace &apos;http://example.org&apos;.</message>
     </error>
   </wsdl>
@@ -1123,7 +923,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0018b</key>
+      <key>Schema-1073b</key>
       <message>The type &apos;{http://example.org}type&apos; has already been defined in another inline XML Schema with the target namespace &apos;http://example.org&apos;.</message>
     </error>
   </wsdl>
@@ -1151,7 +951,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0064</key>
+      <key>Endpoint-1061</key>
       <message>The address &apos;services/EchoService&apos; specified for this endpoint is not an absolute IRI. The address must be absolute.</message>
     </error>
   </wsdl>
@@ -1163,7 +963,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0064</key>
+      <key>Endpoint-1061</key>
       <message>The address &apos;&apos; specified for this endpoint is not an absolute IRI. The address must be absolute.</message>
     </error>
   </wsdl>
@@ -1191,7 +991,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Service-0063</key>
+      <key>Service-1060</key>
       <message>A service with the name &apos;{http://example.org/Service}EchoService&apos; has already been defined for the description component. All services defined in the description component must have unique names.</message>
     </error>
   </wsdl>
@@ -1207,7 +1007,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;NotEchoSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/Service}NotEcho&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -1215,8 +1015,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0066</key>
-      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@258e7a9d&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@250e3a9d&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@26f5fa9d&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
+      <key>Endpoint-1062</key>
+      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@74f33d88&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@74737d88&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@b1dfd88&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -1265,7 +1065,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;binding&apos; does not define bindings for the interface operation &apos;{http://example.org/}operation&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>

Modified: incubator/woden/trunk/java/ant-test/documents-good-report.xml
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/ant-test/documents-good-report.xml?view=diff&rev=546555&r1=546554&r2=546555
==============================================================================
--- incubator/woden/trunk/java/ant-test/documents-good-report.xml (original)
+++ incubator/woden/trunk/java/ant-test/documents-good-report.xml Tue Jun 12 09:20:19 2007
@@ -1955,7 +1955,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}acknowledgedStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -1963,7 +1963,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}silentStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -1975,7 +1975,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}acknowledgedStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -1991,7 +1991,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}store&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -2023,8 +2023,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0066</key>
-      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@29c83a9f&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@1717ba9f&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@15dfba9f&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
+      <key>Endpoint-1062</key>
+      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@275dbdbb&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@3af73dbb&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@234ffdbb&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
     </error>
   </wsdl>
   <wsdl>

Modified: incubator/woden/trunk/java/ant-test/test-suite-results.zip
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/ant-test/test-suite-results.zip?view=diff&rev=546555&r1=546554&r2=546555
==============================================================================
Binary files - no diff available.

Modified: incubator/woden/trunk/java/ant-test/validation-results-without-ids.xml
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/ant-test/validation-results-without-ids.xml?view=diff&rev=546555&r1=546554&r2=546555
==============================================================================
--- incubator/woden/trunk/java/ant-test/validation-results-without-ids.xml (original)
+++ incubator/woden/trunk/java/ant-test/validation-results-without-ids.xml Tue Jun 12 09:20:19 2007
@@ -8,7 +8,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -20,7 +20,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFault-0058</key>
+      <key>BindingFault-1050</key>
       <message>The interface fault specified for this binding fault has already been specified on another binding fault. Each binding fault within a binding must specify a unique interface fault.</message>
     </error>
   </wsdl>
@@ -32,7 +32,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0057</key>
+      <key>Binding-1049</key>
       <message>A binding with the name &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoServiceBinding&apos; has already been defined for the description component. All bindings defined in the description component must have unique names.</message>
     </error>
     <error>
@@ -40,7 +40,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -48,7 +48,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -60,7 +60,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;echoServiceBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echoXML&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -72,7 +72,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -84,7 +84,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -96,7 +96,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -108,7 +108,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0056</key>
+      <key>Binding-1048</key>
       <message>The type &apos;wsdl/http&apos; specified for this binding is not an absolute IRI. The type must be absolute.</message>
     </error>
   </wsdl>
@@ -120,7 +120,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFault-0058</key>
+      <key>BindingFault-1050</key>
       <message>The interface fault specified for this binding fault has already been specified on another binding fault. Each binding fault within a binding must specify a unique interface fault.</message>
     </error>
   </wsdl>
@@ -132,7 +132,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
     <error>
@@ -140,7 +140,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -152,7 +152,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
     <error>
@@ -160,7 +160,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -172,7 +172,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingFaultReference-0062</key>
+      <key>BindingFaultReference-1059</key>
       <message>The binding fault reference must reference an defined interface fault reference.</message>
     </error>
   </wsdl>
@@ -184,7 +184,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingMessageReference-0060</key>
+      <key>BindingMessageReference-1052</key>
       <message>A binding message reference has already been specified for the interface message reference &apos;In&apos;. Each binding message reference within a binding operation component must specify a unique interface message reference.</message>
     </error>
   </wsdl>
@@ -196,7 +196,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>BindingMessageReference-0060</key>
+      <key>BindingMessageReference-1052</key>
       <message>A binding message reference has already been specified for the interface message reference &apos;In&apos;. Each binding message reference within a binding operation component must specify a unique interface message reference.</message>
     </error>
   </wsdl>
@@ -208,8 +208,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1044</key>
+      <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -220,21 +220,13 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1044</key>
+      <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chameleon-1B/getBalance.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/customer/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chameleon-2B/getBalance.wsdl</uri>
@@ -247,22 +239,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/customer/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/getBalance/account/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Chat-1B/Chat-NoBindingInterface.wsdl</uri>
@@ -272,7 +248,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -284,7 +260,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;chatSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/chat.wsdl}say&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -300,7 +276,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Description-0025</key>
+      <key>Description-1006</key>
       <message>The target namespace &apos;example.org/Description&apos; is not an absolute IRI. The target namespace must be an absolute IRI.</message>
     </error>
   </wsdl>
@@ -312,7 +288,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>InterfaceMessageReference-0042</key>
+      <key>InterfaceMessageReference-1029</key>
       <message>An interface message reference with the message label &apos;Out&apos; has already been defined. An interface message reference must have a unique message label within the interface operation that contains it.</message>
     </error>
   </wsdl>
@@ -324,7 +300,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0054</key>
+      <key>Binding-1044</key>
       <message>An interface has not been specified for a binding that specifies operation or fault details. An interface must be specified when operation or fault details are specified.</message>
     </error>
   </wsdl>
@@ -422,23 +398,7 @@
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-1B/XSDImport.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-2B/XSDImportInWSDL.wsdl</uri>
@@ -451,42 +411,10 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-3B/XSDImport2.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/name&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-3B/XSDImportValid.wsdl</uri>
@@ -527,22 +455,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/EchoImpl&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/EchoImpl&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Import-8B/Echo.wsdl</uri>
@@ -571,22 +483,6 @@
       <key>WSDL501</key>
       <message>Expected a &quot;{http://www.w3.org/ns/wsdl}description&quot; element, but found a &quot;{http://www.w3.org/2001/XMLSchema}schema&quot; element instead.</message>
     </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Echo&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Echo&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Interface-1B/Interface.wsdl</uri>
@@ -596,7 +492,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0031</key>
+      <key>Interface-1012</key>
       <message>The styleDefault attribute contains the IRI &apos;wsdl/style/iri&apos;, which is not absolute. All IRIs specified for styleDefault must be absolute.</message>
     </error>
   </wsdl>
@@ -608,7 +504,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
   </wsdl>
@@ -620,7 +516,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface2&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
     <error>
@@ -628,7 +524,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Interface-0027</key>
+      <key>Interface-1009</key>
       <message>This interface extends itself via the extended interface &apos;{http://example.org/}myInterface&apos;. An interface cannot appear in the list of interfaces it extends.</message>
     </error>
   </wsdl>
@@ -652,7 +548,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -672,15 +568,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
@@ -692,41 +580,17 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
+      <key>Schema-1066</key>
       <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-1B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-2B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-3B/InterfaceMessageReference.wsdl</uri>
@@ -736,21 +600,13 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>InterfaceMessageReference-0042</key>
+      <key>InterfaceMessageReference-1029</key>
       <message>An interface message reference with the message label &apos;myLabel&apos; has already been defined. An interface message reference must have a unique message label within the interface operation that contains it.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceMessageReference-4B/InterfaceMessageReference.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/InterfaceOperation-1B/echo-extended.wsdl</uri>
@@ -760,16 +616,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://www.wso2.com/schemas/2006/interop/EchoService&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://www.wso2.com/schemas/2006/interop/EchoService&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
+      <key>Binding-1045</key>
+      <message>The binding &apos;echoServiceSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://www.wso2.com/wsdl/2006/interop/EchoService}echo&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -784,7 +632,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>MEP-0037</key>
+      <key>MEP-1022</key>
       <message>The message exchange pattern &apos;wsdl/in-out&apos; is not absolute. A message exchange pattern must be identified by an absolute IRI.</message>
     </error>
   </wsdl>
@@ -820,7 +668,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -832,7 +680,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -844,7 +692,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -856,7 +704,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/Echo&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -1027,7 +875,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0017</key>
+      <key>Schema-1069</key>
       <message>The XML schema imported from &apos;Schema.xsd&apos; must specify a target namespace.</message>
     </error>
     <error>
@@ -1035,7 +883,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/schema/&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
@@ -1047,69 +895,21 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0052</key>
+      <key>Schema-1070</key>
       <message>The imported XML Schema is not defined with the namespace &apos;http://example.org/schema/&apos; that is specified on the import element.</message>
     </error>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-3B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-4B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-5B/Schema.wsdl</uri>
-    <success>false</success>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
-    <error>
-      <errorLocator>
-        <lineNumber>0</lineNumber>
-        <columnNumber>0</columnNumber>
-      </errorLocator>
-      <key>Schema-0016</key>
-      <message>A component in the XML Schema namespace &apos;http://example.org/Person/&apos; has been referenced but this namespace is not available. In order to reference components from a XML Schema namespace the namespace must be imported or defined inline.</message>
-    </error>
+    <success>true</success>
   </wsdl>
   <wsdl>
     <uri>file:/C:/workspace/woden/woden/downloads/w3c/documents/bad/Schema-5B/SchemaContainer.wsdl</uri>
@@ -1123,7 +923,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0018</key>
+      <key>Schema-1073</key>
       <message>The element &apos;{http://example.org}element&apos; has already been defined in another inline XML Schema with the target namespace &apos;http://example.org&apos;.</message>
     </error>
   </wsdl>
@@ -1135,7 +935,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Schema-0018b</key>
+      <key>Schema-1073b</key>
       <message>The type &apos;{http://example.org}type&apos; has already been defined in another inline XML Schema with the target namespace &apos;http://example.org&apos;.</message>
     </error>
   </wsdl>
@@ -1163,7 +963,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0064</key>
+      <key>Endpoint-1061</key>
       <message>The address &apos;services/EchoService&apos; specified for this endpoint is not an absolute IRI. The address must be absolute.</message>
     </error>
   </wsdl>
@@ -1175,7 +975,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0064</key>
+      <key>Endpoint-1061</key>
       <message>The address &apos;&apos; specified for this endpoint is not an absolute IRI. The address must be absolute.</message>
     </error>
   </wsdl>
@@ -1203,7 +1003,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Service-0063</key>
+      <key>Service-1060</key>
       <message>A service with the name &apos;{http://example.org/Service}EchoService&apos; has already been defined for the description component. All services defined in the description component must have unique names.</message>
     </error>
   </wsdl>
@@ -1219,7 +1019,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;NotEchoSOAPBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/Service}NotEcho&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -1227,8 +1027,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0066</key>
-      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@6ba1fab0&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@6b21bab0&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@6a9e3ab0&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
+      <key>Endpoint-1062</key>
+      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@160b3d92&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@158b7d92&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@1515fd92&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
     </error>
   </wsdl>
   <wsdl>
@@ -1277,7 +1077,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;binding&apos; does not define bindings for the interface operation &apos;{http://example.org/}operation&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -3244,7 +3044,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}acknowledgedStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
     <error>
@@ -3252,7 +3052,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}silentStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -3264,7 +3064,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}acknowledgedStorage&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -3280,7 +3080,7 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Binding-0055</key>
+      <key>Binding-1045</key>
       <message>The binding &apos;storageBinding&apos; does not define bindings for the interface operation &apos;{http://example.org/soapStorage}store&apos;. When a binding specifies an interface it must specify bindings for all of the interfaces operations.</message>
     </error>
   </wsdl>
@@ -3312,8 +3112,8 @@
         <lineNumber>0</lineNumber>
         <columnNumber>0</columnNumber>
       </errorLocator>
-      <key>Endpoint-0066</key>
-      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@1e843a9b&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@1bd0fa9b&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@ca43a9b&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
+      <key>Endpoint-1062</key>
+      <message>The binding &apos;org.apache.woden.internal.wsdl20.BindingImpl@76f5bd8f&apos; specified for this endpoint specifies the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@79127d8f&apos; and not the interface &apos;org.apache.woden.internal.wsdl20.InterfaceImpl@652ffd8f&apos; specified by the service. The binding specified for this endpoint must either not specify an interface or specify the same interface as the service.</message>
     </error>
   </wsdl>
   <wsdl>



---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


Mime
View raw message