Author: lmandel
Date: Mon Nov 14 23:39:51 2005
New Revision: 344325
URL: http://svn.apache.org/viewcvs?rev=344325&view=rev
Log:
Added validation assertions.
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=344325&r1=344324&r2=344325&view=diff
==============================================================================
--- incubator/woden/java/src/org/apache/woden/internal/Messages.properties
(original)
+++ incubator/woden/java/src/org/apache/woden/internal/Messages.properties Mon
Nov 14 23:39:51 2005
@@ -43,6 +43,7 @@
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.
WSDL013=Could not create a URL from context URI "{0}" and location URI "{1}".
WSDL014=Could not locate the WSDL document at URL "{0}".
@@ -53,15 +54,66 @@
# 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
# specific part of the WSDL spec that the error relates to).
+# The error codes listed below match the assertion ids in the WSDL 2.0
specification.
+# The error code itself is a key for the error message.
+# The error code ref is a reference to the location in the specification that
+# describes the assertion.
+# The error code assertion is the text of the assertion from the specification.
-
+# 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}".
-WSDL501=The XML schema imported from "{0}" must specify a target namespace.
-WSDL502=The namespace "{0}" specified on a schema import element does not
match the target namespace "{1}" of the schema at the schemaLocation "{2}".
-WSDL503=An XML schema is missing its target namespace attribute. Schema id is
"{0}".
+
+
+# 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}".
+
+
+schema-0016 =
+schema-0016.ref = 3.1
+schema-0016.assertion = A WSDL 2.0 document MUST NOT refer to XML Schema
components in a given namespace unless an xs:import or xs:schema element
information item for that namespace is present or the namespace is the XML
Schema namespace which contains built-in types as defined in XML Schema Part 2:
Datatypes Second Edition [XML Schema: Datatypes].
+
+# schema-0017 is a replacement for WSDL501
+WSDL501=The XML schema imported from "{0}" must specify a target namespace.
+schema-0017 = The XML schema imported from "{0}" must specify a target
namespace of "{1}".
+schema-0017.ref = 3.1.1.1
+schema-0017.assertion = The referenced schema MUST contain a targetNamespace
attribute information item on its xs:schema element information item and the
values of these two attribute information items MUST be identical.
+
+
+#schema-0017b is a replacement for WSDL502
+WSDL502=The namespace "{0}" specified on a schema import element does not
match the target namespace "{1}" of the schema at the schemaLocation "{2}".
+schema-0017b = The namespace "{0}" specified on the XML schema import element
does not match the target namespace "{1}" specified in the XML schema document
located at "{2}".
+schema-0017b.ref = 3.1.2.1
+schema-0017b.assertion = The targetNamespace attribute information item
defines the namespace of the element declarations and type definitions inlined
in its [owner element] xs:schema element information item. WSDL 2.0 modifies
the XML Schema definition of the xs:schema element information item to make
this attribute information item required.
+
+schema-0018 =
+schema-0018.ref = 3.1.2
+schema-0018.assertion = For example, two or more inlined schemas may have the
same targetNamespace provided that they do not define the same elements or
types.
+
+# error schema-0019 is a replacement for WSDL503
+WSDL503=An XML schema is missing its target namespace attribute. Schema id is
"{0}"
+schema-0019 = The XML schema does not define a target namespace. WSDL 2.0
modifies the XML Schema definition of the xs:schema element information item to
make the targetNamespace attribute information item required.
+schema-0019.ref = 3.1.2.1
+schema-0019.assertion = The targetNamespace attribute information item defines
the namespace of the element declarations and type definitions inlined in its
[owner element] xs:schema element information item. WSDL 2.0 modifies the XML
Schema definition of the xs:schema element information item to make this
attribute information item required.
+
+schema-0020 =
+schema-0020.ref = 3.1.3
+schema-0020.assertion = An element attribute information item MUST NOT refer
to a global xs:simpleType or xs:complexType definition.
+
+schema-0021 =
+schema-0021.ref = 3.2
+schema-0021.assertion = A specification of extension syntax for an alternative
schema language MUST use a namespace that is different than the namespace of
XML Schema. The namespace of the alternative schema language is used for
element information items that are children of the wsdl:types element
information item and for any extensibility attribute information items that
appear on other components. The namespace MUST be an absolute IRI.
+
+schema-0022 =
+schema-0022.ref = 3.3.3
+schema-0022.assertion = The wsdlx:interface and wsdlx:binding attributes may
be used either independently or together. If they are used together then they
MUST satisfy the same consistency rules that apply to the {interface} property
of a Service component and the {binding} property of a nested Endpoint
component, that is either the binding refers the interface or the binding
refers to no interface.
+
+types-0023 =
+types-0023.ref = 3.2
+types-0023.assertion = A specification of extension syntax for an alternative
schema language MUST include the declaration of an element information item,
intended to appear as a child of the wsdl:types element information item, which
references, names, and locates the schema instance (an ?import? element
information item).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
