You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by jk...@apache.org on 2005/12/04 01:02:47 UTC

svn commit: r352052 - /incubator/woden/java/src/org/apache/woden/internal/Messages.properties

Author: jkaputin
Date: Sat Dec  3 16:02:41 2005
New Revision: 352052

URL: http://svn.apache.org/viewcvs?rev=352052&view=rev
Log:
Reorganized the non-WSDL Assertion errors into System
Config and Parsing errors. 
No changes to the error ids or message contents yet. 
No deletions yet.
No changes to the WSDL Assertion Errors section. 

Modified:
    incubator/woden/java/src/org/apache/woden/internal/Messages.properties

Modified: incubator/woden/java/src/org/apache/woden/internal/Messages.properties
URL: http://svn.apache.org/viewcvs/incubator/woden/java/src/org/apache/woden/internal/Messages.properties?rev=352052&r1=352051&r2=352052&view=diff
==============================================================================
--- incubator/woden/java/src/org/apache/woden/internal/Messages.properties (original)
+++ incubator/woden/java/src/org/apache/woden/internal/Messages.properties Sat Dec  3 16:02:41 2005
@@ -32,24 +32,29 @@
 #
 ############################################################
 
+# TODO post-milestone2, resort and renumber the System Config and Parsing errors (JK)
 
-# ------------SECTION 1: System errors -------------------------
+# ------------ System Config errors ---------------------
 
 WSDL001=###Not used yet###
 WSDL002={0} Parser configuration error.
-WSDL003={0} Parsing error in document located at {1}.
-WSDL004=Expected a "{0}" element, but found a "{1}" element instead.
 WSDL005=The feature name must not be null when attempting to get or set a named feature.
 WSDL006=The feature name "{0}" is not recognized.
 WSDL007=The property name must not be null when attempting to get or set a named property.
 WSDL008=The property name "{0}" is not recognized.
-! TODO: This may not be necessary if using schema validation.
-WSDL009=The WSDL description at location "{0}" is missing its target namespace attribute. 
+
+# ------------ Parsing errors -------------------
+
+WSDL003={0} Parsing error in document located at {1}.
+WSDL004=Expected a "{0}" element, but found a "{1}" element instead.
 WSDL013=Could not create a URL from context URI "{0}" and location URI "{1}".
 WSDL014=Could not locate the WSDL document at URL "{0}".
 WSDL015=Could not locate the schema document at URL "{0}"
+WSDL504=Problem creating a QName from the string "{0}" in element "{1}".
+WSDL506=Could not create a URI from the string "{0}".
+WSDL507=Could not create a QName from the string "{0}".
 
-# ------------SECTION 2: WSDL-related errors -------------------
+# ------------ TODO determine if these errors are needed -------------------
 
 # TODO - replace WSDL5xx error codes with reference numbers from the asserts
 #        to be defined in the WSDL spec (i.e. err msg nos. that point to the
@@ -60,16 +65,14 @@
 # describes the assertion.
 # The error code assertion is the text of the assertion from the specification.
 
+! TODO: This may not be necessary if using schema validation.
+WSDL009=The WSDL description at location "{0}" is missing its target namespace attribute. 
+
 # This should be caught be schema validation. Is this error message necessary?
 WSDL500=The namespace attribute is missing from a schema import element <xs:import>. The schemaLocation attribute is "{0}". The base document URI of the importing WSDL is "{1}".
 
-
-# TODO: Is this really a WSDL semantic error or just a parsing error?
-WSDL504=Problem creating a QName from the string "{0}" in element "{1}".
 # This should be caught by schema validation. Is this error message necessary?
 WSDL505=The "{0}" attribute is missing from a "{1}" element.
-# TODO: Is this really a WSDL semantic error or just a parsing error?
-WSDL506=Could not create a URI from the string "{0}".
 
 # ---------------- WSDL Document Level Assertions -------------------
 



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