Modified:
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
URL:
http://svn.apache.org/viewvc/incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties?rev=568932&r1=568931&r2=568932&view=diff
==============================================================================
---
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
(original)
+++
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
Thu Aug 23 04:01:23 2007
@@ -1,292 +1,292 @@
-############################################################
-# Licensed to the Apache Software Foundation (ASF) under one or more
-# contributor license agreements. See the NOTICE file distributed with
-# this work for additional information regarding copyright ownership.
-# The ASF licenses this file to You under the Apache License, Version 2.0
-# (the "License"); you may not use this file except in compliance with
-# the License. You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#############################################################
-
-############################################################
-#
-# Filename: Messages.properties
-#
-# This file contains the text for all messages produced by Woden.
-# Each message is keyed by a message number. The file is used as
-# a ResourceBundle by Woden.
-#
-# The messages are separated into two groups - those that relate
-# to System type problems (e.g. Woden or parser configuration)
-# and those that relate specifically to processing WSDL documents
-# (i.e. related to the rules defined in the WSDL spec). The
-# latter group of messages will eventually correspond to asserts
-# being added to the W3C WSDL spec and the message numbers will
-# be replaced with corresponding assert references.
-#
-############################################################
-
-# TODO post-milestone2, resort and renumber the System Config and Parsing
errors (JK)
-
-# ------------ System Config errors ---------------------
-
-WSDL001=###Not used yet###
-WSDL002={0} Parser configuration error.
-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.
-WSDL009=Could not instantiate the "{0}" class.
-WSDL010=The extension attribute "{0}" in the context of "{1}" does not have a
Java class registered, so it will map to "{2}" by default.
-WSDL011=The Java class "{0}" does not implement the "Attr" interface.
-WSDL012=No Java type was registered for the extension element "{0}" in the
context of "{1}".
-WSDL013=The Java class "{0}" does not implement the "ExtensionElement"
interface.
-WSDL014=Cannot specify a null Extension Registry.
-WSDL015=The extension namespace "{0}" in the context of "{1}" does not have a
Java class registered.
-WSDL016=The Java class "{0}" does not implement the "ComponentExtensions"
interface.
-WSDL017=WSDL source represented by the type "{0}" cannot be read by the
WSDLReader implementation class "{1}".
-WSDL018=WSDL cannot be represented by the type "{0}" in the WSDLSource
implementation class "{1}".
-WSDL019=A WSDL element cannot be represented by the type "{0}" in the
XMLElement implementation class "{1}".
-
-# ------------ Parsing errors -------------------
-
-WSDL500={0} Parsing error in document located at {1}.
-WSDL501=Expected a "{0}" element, but found a "{1}" element instead.
-WSDL502=Could not create a URL from context URI "{0}" and location URI "{1}".
-WSDL503=Could not locate the WSDL document at URL "{0}".
-WSDL504=Could not locate the schema document at URL "{0}"
-WSDL505=Could not create 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}".
-WSDL508=Could not create a String from a null value.
-WSDL509=Could not create a list of QNames from the string "{0}".
-WSDL510=Could not create a QName from the string "{0}" within the string of
QNames "{1}".
-WSDL511=Boolean defaulted to 'false' due to invalid boolean string "{0}".
-WSDL512=Could not create an Integer from the string "{0}".
-WSDL513=Could not determine the namespace for prefixed value "{0}" in element
"{1}".
-
-WSDL520=Extension element "{0}" in the context of "{1}" must not be in the
WSDL namespace.
-WSDL521=Could not parse an inline schema in the WSDL at URL "{0}".
-WSDL522=Could not parse a schema imported from URL "{0}".
-WSDL523=The QName of an extension attribute must not be null.
-WSDL524=URI resolution failed on URI "{0}".
-WSDL523=Cannot add a new TypesElement as one already exists in the
DescriptionElement.
-
-# ------------ 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
-# 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.
-
-
-# ---------------- WSDL Document Level Assertions -------------------
-
-Description-1006 = The target namespace ''{0}'' is not an absolute IRI. The
target namespace must be an absolute IRI.
-Description-1006.assertion = The type of the targetNamespace attribute
information item is xs:anyURI. Its value MUST be an absolute IRI (see [IETF RFC
3987]).
-
-Import-0001 = The component ''{0}'' is in the namespace ''{1}'', which has not
been imported. A namespace must be imported before components from it can be
referenced in this document.
-Import-0001.assertion = However, any WSDL 2.0 document that contains
component definitions that refer by QName to WSDL 2.0 components that belong to
a different namespace MUST contain a wsdl:import element information item for
that namespace (see 4.2 Importing Descriptions).
-
-Import-0003 = The imported document located at ''{0}'' has the same namespace
as this document. An imported document's target namespace must be different
than the target namespace of the document that imports it. If the target
namespaces are the same a WSDL include should be used instead of a WSDL import.
-Import-0003.assertion = Imported components have different target namespace
values from the WSDL 2.0 document that is importing them.
-
-Interface-1012 = The styleDefault attribute contains the IRI ''{0}'', which is
not absolute. All IRIs specified for styleDefault must be absolute.
-Interface-1012.assertion = The type of the styleDefault attribute information
item is list of xs:anyURI. Its value, if present, MUST contain absolute IRIs
(see [IETF RFC 3987]).
-
-MessageLabel-0004 =
-MessageLabel-0004.assertion = The messageLabel attribute information item of
an interface message reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
-
-MessageLabel-1041 =
-MessageLabel-1041.assertion = The messageLabel attribute information item of
an interface fault reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
-
-MessageLabel-0006 =
-MessageLabel-0006.assertion = The messageLabel attribute information item of
a binding message reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
-
-MessageLabel-1056 =
-MessageLabel-1056.assertion = The messageLabel attribute information item of
a binding fault reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
-
-MessageLabel-1030 =
-MessageLabel-1030.assertion = If the messageLabel attribute information item
of an interface message reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
-
-MessageLabel-1042 =
-MessageLabel-1042.assertion = If the messageLabel attribute information item
of an interface fault reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
-
-MessageLabel-1053 =
-MessageLabel-1053.assertion = If the messageLabel attribute information item
of a binding message reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
-
-MessageLabel-1057 =
-MessageLabel-1057.assertion = If the messageLabel attribute information item
of a binding fault reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
-
-MessageLabel-1031 =
-MessageLabel-1031.assertion = If the messageLabel attribute information item
of an interface message reference element information item is absent then
there MUST be a unique placeholder message with {direction} equal to the
message direction.
-
-MessageLabel-1043 =
-MessageLabel-1043.assertion = If the messageLabel attribute information item
of an interface fault reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
-
-MessageLabel-1054 =
-MessageLabel-1054.assertion = If the messageLabel attribute information item
of a binding message reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
-
-MessageLabel-1058 =
-MessageLabel-1058.assertion = If the messageLabel attribute information item
of a binding fault reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
-
-Schema-1066 = The schema component ''{0}'' in the namespace ''{1}'' cannot be
referenced unless this namespace is imported by an xs:import element or is the
target namespace of an inlined xs:schema element.
-Schema-1066.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, http://www.w3.org/2001/XMLSchema, which contains built-in
types as defined in XML Schema Part 2: Datatypes Second Edition [XML Schema:
Datatypes].
-
-Schema-1069 = The XML schema imported from ''{0}'' must specify a target
namespace.
-Schema-1069.assertion = The referenced schema MUST contain a targetNamespace
attribute information item on its xs:schema element information item.
-
-#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-1073 = The element ''{0}'' has already been defined in another inline
XML Schema with the target namespace ''{1}''.
-Schema-1073.assertion = A WSDL 2.0 document MUST NOT define the same element
or type in more than one inlined schema.
-
-Schema-1073b = The type ''{0}'' has already been defined in another inline XML
Schema with the target namespace ''{1}''.
-Schema-1073b.assertion = A WSDL 2.0 document MUST NOT define the same element
or type in more than one inlined schema.
-
-Schema-1075 = The alternative schema language makes use of the XML Schema
namespace.
-Schema-1075.assertion = A specification of extension syntax for an alternative
schema language MUST use a namespace that is different than the namespace of
XML Schema.
-
-Schema-1079 = The binding ''{0}'' specified is not consistent with the
interface ''{1}'' specified. The binding must refer to the same interface as is
specified by the interace attribute.
-Schema-1079.assertion = If wsdlx:interface and wsdlx:binding 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 of the service or
the binding refers to no interface.
-
-Schema-1070 = The imported XML Schema is not defined with the namespace
''{0}'' that is specified on the import element.
-Schema-1070.assertion = The value of the targetNamespace attribute information
item of the xs:schema element information item of an imported schema MUST equal
the value of the namespace of the import element information item in the
importing WSDL 2.0 document.
-
-Schema-1076 = The namespace ''{0}'' specified is not an absolute IRI.
-Schema-1076.assertion = The namespace used for an alternate schema language
MUST be an absolute IRI.
-
-Types-1074 = The alternate schema language does not include a declaration of
an element information item to appear as a child of the types element.
-Types-1074.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).
-
-
-# ---------------- WSDL Component Level Assertions -------------------
-
-# If a Binding component specifies any operation-specific binding details (by
including Binding Operation components) or any fault binding details (by
including Binding Fault components) then it MUST specify an interface the
Binding component applies to, so as to indicate which interface the operations
come from.
-Binding-1044 = 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.
-
-# A Binding component that defines bindings for an Interface component MUST
define bindings for all the operations of that Interface component.
-Binding-1045 = The binding ''{0}'' does not define bindings for the interface
operation ''{1}''. When a binding specifies an interface it must specify
bindings for all of the interface's operations.
-
-# This xs:anyURI MUST be an absolute IRI as defined by [IETF RFC 3987].
-Binding-1048 = The type ''{0}'' specified for this binding is not an absolute
IRI. The type must be absolute.
-
-# For each Binding component in the {bindings} property of a Description
component, the {name} property MUST be unique.
-Binding-1049 = A binding with the name ''{0}'' has already been defined for
the description component. All bindings defined in the description component
must have unique names.
-
-# For each Binding Fault component in the {binding faults} property of a
Binding component, the {interface fault} property MUST be unique.
-BindingFault-1050 = 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.
-
-# For each Binding Fault Reference component in the {binding fault references}
property of a Binding Operation component, the {interface fault reference}
property MUST be unique.
-BindingFaultReference-1055 = A binding fault reference has already been
specified for the interface fault reference ''{0}''. Each binding fault
reference within a binding operation component must specify a unique interface
fault reference.
-
-# There MUST be an Interface Fault Reference component in the {interface fault
references} of the Interface Operation being bound with {message label} equal
to the effective message label and with {interface fault} equal to an Interface
Fault component with {name} equal to the actual value of the ref attribute
information item.
-BindingFaultReference-1059 = The binding fault reference must reference an
defined interface fault reference.
-
-# For each Binding Message Reference component in the {binding message
references} property of a Binding Operation component, the {interface message
reference} property MUST be unique.
-BindingMessageReference-1052 = A binding message reference has already been
specified for the interface message reference ''{0}''. Each binding message
reference within a binding operation component must specify a unique interface
message reference.
-
-# For each Binding Operation component in the {binding operations} property of
a Binding component, the {interface operation} property MUST be unique.
-BindingOperation-1051 = A binding operation has already been specified for the
interface operation ''{0}''. Each binding operation within a binding component
must specify a unique interface operation.
-
-Description-0024 =
-Description-0024.ref = 2.1.2
-Description-0024.assertion = Each WSDL 2.0 or type system component MUST be
uniquely identified by its qualified name.
-
-# This xs:anyURI MUST be an absolute IRI as defined by [IETF RFC 3987].
-Endpoint-1061 = The address ''{0}'' specified for this endpoint is not an
absolute IRI. The address must be absolute.
-
-# For each Endpoint component in the {endpoints} property of a Service
component, the {binding} property MUST either be a Binding component with an
unspecified {interface} property or a Binding component with an {interface}
property equal to the {interface} property of the Service component.
-Endpoint-1062 = The binding ''{0}'' specified for this endpoint specifies the
interface ''{1}'' and not the interface ''{2}'' specified by the service. The
binding specified for this endpoint must either not specify an interface or
specify the same interface as the service.
-
-Interface-1009 = This interface extends itself via the extended interface
''{0}''. An interface cannot appear in the list of interfaces it extends.
-Interface-1009.ref = 2.2.1
-Interface-1009.assertion = To avoid circular definitions, an interface MUST
NOT appear as an element of the set of interfaces it extends, either directly
or indirectly.
-
-Interface-1010 = An interface with the name ''{0}'' has already been defined
for the description component. All interfaces defined in the description
component must have unique names.
-Interface-1010.ref = 2.2.1
-Interface-1010.assertion = For each Interface component in the {interfaces}
property of a Description component, the {name} property MUST be unique.
-
-InterfaceFault-1015 =
-InterfaceFault-1015.ref = 2.3.1
-InterfaceFault-1015.assertion = In cases where, due to an interface extending
one or more other interfaces, two or more Interface Fault components have the
same value for their {name} property, then the component models of those
Interface Fault components MUST be equivalent (see 2.17 Equivalence of
Components).
-
-InterfaceFaultReference-1037 =
-InterfaceFaultReference-1037.ref = 2.6.1
-InterfaceFaultReference-1037.assertion = The value of this property MUST match
the name of a placeholder message defined by the message exchange pattern.
-
-InterfaceFaultReference-1038 =
-InterfaceFaultReference-1038.ref = 2.6.1
-InterfaceFaultReference-1038.assertion = The direction MUST be consistent with
the direction implied by the fault propagation ruleset used in the message
exchange pattern of the operation.
-
-InterfaceFaultReference-1039 = An interface fault reference with for the fault
''{0}'' and message label ''{1}'' has already been defined for this interface
operation. Each fault reference in an interface operation must have a unique
combination of fault and message label.
-InterfaceFaultReference-1039.ref = 2.6.1
-InterfaceFaultReference-1039.assertion = For each Interface Fault Reference
component in the {interface fault references} property of an Interface
Operation component, the combination of its {interface fault} and {message
label} properties MUST be unique.
-
-InterfaceMessageReference-1026 =
-InterfaceMessageReference-1026.ref = 2.5.1
-InterfaceMessageReference-1026.assertion = The direction MUST be the same as
the direction of the message identified by the {message label} property in the
{message exchange pattern} of the Interface Operation component this is
contained within.
-
-InterfaceMessageReference-1028 = The message content model is #any or #none
and the element declaration is not empty. The element declaration must be empty
when the message content model is #any or #none.
-InterfaceMessageReference-1028.ref = 2.5.1
-InterfaceMessageReference-1028.assertion = When the {message content model}
property has the value #any or #none the {element declaration} property MUST be
empty.
-
-InterfaceMessageReference-1029 = An interface message reference with the
message label ''{0}'' has already been defined. An interface message reference
must have a unique message label within the interface operation that contains
it.
-InterfaceMessageReference-1029.ref = 2.5.1
-InterfaceMessageReference-1029.assertion = For each Interface Message
Reference component in the {interface message references} property of an
Interface Operation component, its {message label} property MUST be unique.
-
-InterfaceOperation-20970 =
-InterfaceOperation-20970 = 2.4.1
-InterfaceOperation-20970.assertion = In cases where, due to an interface
extending one or more other interfaces, two or more Interface Operation
components have the same value for their {name} property, then the component
models of those Interface Operation components MUST be equivalent (see 2.17
Equivalence of Components).
-
-InterfaceOperation-20973 =
-InterfaceOperation-20973.ref = 2.4.1.2
-InterfaceOperation-20973.assertion = An Interface Operation component MUST
satisfy the specification defined by each operation style identified by its
{style} property.
-
-MEP-1022 = The message exchange pattern ''{0}'' is not absolute. A message
exchange pattern must be identified by an absolute IRI.
-MEP-1022.ref = 2.4.1.1
-MEP-1022.assertion = A message exchange pattern is uniquely identified by an
absolute IRI which is used as the value of the {message exchange pattern}
property the Interface Operation component, and it specifies the fault
propagation ruleset that its faults obey.
-
-MessageLabel-1024 =
-MessageLabel-1024.ref = 2.5.1
-MessageLabel-1024.assertion = The value of this property MUST match the name
of a placeholder message defined by the message exchange pattern.
-
-QName-0002 =
-QName-0002.assertion = Furthermore, all QName references, whether to the same
of to difference namespace MUST resolve to components (see 2.1.9 QName
resolution).
-
-# For each Service component in the {services} property of a Description
component, the {name} property MUST be unique.
-Service-1060 = A service with the name ''{0}'' has already been defined for
the description component. All services defined in the description component
must have unique names.
-
-Types-1008 =
-Types-1008.ref = 2.1.2.1
-Types-1008.assertion = It is an error if there are multiple type definitions
for each QName.
-
-# ------------SECTION 3: WSDL-related warnings -------------------
-# These warnings were pulled from the WSDL 2.0 spec and are possible warnings
-# for the validator to report.
-
-Description-S0001 =
-Description-S0001.ref = 2.1.2
-Description-S0001.assertion = The value of the targetNamespace attribute
information item SHOULD be a dereferenceable IRI (see [IETF RFC 3987])
-
-InterfaceFault-S0002 =
-InterfaceFault-S0002.ref = 2.3.1
-InterfaceFault-S0002.assertion = For the above reason, it is considered good
practice to ensure, where necessary, that the local name of the {name} property
of Interface Fault components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
-
-InterfaceOperation-S0003 =
-InterfaceOperation-S0003.ref = 2.4.1
-InterfaceOperation-S0003.assertion = For the above reason, it is considered
good practice to ensure, where necessary, that the {name} property of Interface
Operation components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
-
+############################################################
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#############################################################
+
+############################################################
+#
+# Filename: Messages.properties
+#
+# This file contains the text for all messages produced by Woden.
+# Each message is keyed by a message number. The file is used as
+# a ResourceBundle by Woden.
+#
+# The messages are separated into two groups - those that relate
+# to System type problems (e.g. Woden or parser configuration)
+# and those that relate specifically to processing WSDL documents
+# (i.e. related to the rules defined in the WSDL spec). The
+# latter group of messages will eventually correspond to asserts
+# being added to the W3C WSDL spec and the message numbers will
+# be replaced with corresponding assert references.
+#
+############################################################
+
+# TODO post-milestone2, resort and renumber the System Config and Parsing
errors (JK)
+
+# ------------ System Config errors ---------------------
+
+WSDL001=###Not used yet###
+WSDL002={0} Parser configuration error.
+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.
+WSDL009=Could not instantiate the "{0}" class.
+WSDL010=The extension attribute "{0}" in the context of "{1}" does not have a
Java class registered, so it will map to "{2}" by default.
+WSDL011=The Java class "{0}" does not implement the "Attr" interface.
+WSDL012=No Java type was registered for the extension element "{0}" in the
context of "{1}".
+WSDL013=The Java class "{0}" does not implement the "ExtensionElement"
interface.
+WSDL014=Cannot specify a null Extension Registry.
+WSDL015=The extension namespace "{0}" in the context of "{1}" does not have a
Java class registered.
+WSDL016=The Java class "{0}" does not implement the "ComponentExtensions"
interface.
+WSDL017=WSDL source represented by the type "{0}" cannot be read by the
WSDLReader implementation class "{1}".
+WSDL018=WSDL cannot be represented by the type "{0}" in the WSDLSource
implementation class "{1}".
+WSDL019=A WSDL element cannot be represented by the type "{0}" in the
XMLElement implementation class "{1}".
+
+# ------------ Parsing errors -------------------
+
+WSDL500={0} Parsing error in document located at {1}.
+WSDL501=Expected a "{0}" element, but found a "{1}" element instead.
+WSDL502=Could not create a URL from context URI "{0}" and location URI "{1}".
+WSDL503=Could not locate the WSDL document at URL "{0}".
+WSDL504=Could not locate the schema document at URL "{0}"
+WSDL505=Could not create 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}".
+WSDL508=Could not create a String from a null value.
+WSDL509=Could not create a list of QNames from the string "{0}".
+WSDL510=Could not create a QName from the string "{0}" within the string of
QNames "{1}".
+WSDL511=Boolean defaulted to 'false' due to invalid boolean string "{0}".
+WSDL512=Could not create an Integer from the string "{0}".
+WSDL513=Could not determine the namespace for prefixed value "{0}" in element
"{1}".
+
+WSDL520=Extension element "{0}" in the context of "{1}" must not be in the
WSDL namespace.
+WSDL521=Could not parse an inline schema in the WSDL at URL "{0}".
+WSDL522=Could not parse a schema imported from URL "{0}".
+WSDL523=The QName of an extension attribute must not be null.
+WSDL524=URI resolution failed on URI "{0}".
+WSDL523=Cannot add a new TypesElement as one already exists in the
DescriptionElement.
+
+# ------------ 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
+# 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.
+
+
+# ---------------- WSDL Document Level Assertions -------------------
+
+Description-1006 = The target namespace ''{0}'' is not an absolute IRI. The
target namespace must be an absolute IRI.
+Description-1006.assertion = The type of the targetNamespace attribute
information item is xs:anyURI. Its value MUST be an absolute IRI (see [IETF RFC
3987]).
+
+Import-0001 = The component ''{0}'' is in the namespace ''{1}'', which has not
been imported. A namespace must be imported before components from it can be
referenced in this document.
+Import-0001.assertion = However, any WSDL 2.0 document that contains
component definitions that refer by QName to WSDL 2.0 components that belong to
a different namespace MUST contain a wsdl:import element information item for
that namespace (see 4.2 Importing Descriptions).
+
+Import-0003 = The imported document located at ''{0}'' has the same namespace
as this document. An imported document's target namespace must be different
than the target namespace of the document that imports it. If the target
namespaces are the same a WSDL include should be used instead of a WSDL import.
+Import-0003.assertion = Imported components have different target namespace
values from the WSDL 2.0 document that is importing them.
+
+Interface-1012 = The styleDefault attribute contains the IRI ''{0}'', which is
not absolute. All IRIs specified for styleDefault must be absolute.
+Interface-1012.assertion = The type of the styleDefault attribute information
item is list of xs:anyURI. Its value, if present, MUST contain absolute IRIs
(see [IETF RFC 3987]).
+
+MessageLabel-0004 =
+MessageLabel-0004.assertion = The messageLabel attribute information item of
an interface message reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
+
+MessageLabel-1041 =
+MessageLabel-1041.assertion = The messageLabel attribute information item of
an interface fault reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
+
+MessageLabel-0006 =
+MessageLabel-0006.assertion = The messageLabel attribute information item of
a binding message reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
+
+MessageLabel-1056 =
+MessageLabel-1056.assertion = The messageLabel attribute information item of
a binding fault reference element information item MUST be present if the
message exchange pattern has more than one placeholder message with {direction}
equal to the message direction.
+
+MessageLabel-1030 =
+MessageLabel-1030.assertion = If the messageLabel attribute information item
of an interface message reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
+
+MessageLabel-1042 =
+MessageLabel-1042.assertion = If the messageLabel attribute information item
of an interface fault reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
+
+MessageLabel-1053 =
+MessageLabel-1053.assertion = If the messageLabel attribute information item
of a binding message reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
+
+MessageLabel-1057 =
+MessageLabel-1057.assertion = If the messageLabel attribute information item
of a binding fault reference element information item is present then its
actual value MUST match the {message label} of some placeholder message with
{direction} equal to the message direction.
+
+MessageLabel-1031 =
+MessageLabel-1031.assertion = If the messageLabel attribute information item
of an interface message reference element information item is absent then
there MUST be a unique placeholder message with {direction} equal to the
message direction.
+
+MessageLabel-1043 =
+MessageLabel-1043.assertion = If the messageLabel attribute information item
of an interface fault reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
+
+MessageLabel-1054 =
+MessageLabel-1054.assertion = If the messageLabel attribute information item
of a binding message reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
+
+MessageLabel-1058 =
+MessageLabel-1058.assertion = If the messageLabel attribute information item
of a binding fault reference element information item is absent then there
MUST be a unique placeholder message with {direction} equal to the message
direction.
+
+Schema-1066 = The schema component ''{0}'' in the namespace ''{1}'' cannot be
referenced unless this namespace is imported by an xs:import element or is the
target namespace of an inlined xs:schema element.
+Schema-1066.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, http://www.w3.org/2001/XMLSchema, which contains built-in
types as defined in XML Schema Part 2: Datatypes Second Edition [XML Schema:
Datatypes].
+
+Schema-1069 = The XML schema imported from ''{0}'' must specify a target
namespace.
+Schema-1069.assertion = The referenced schema MUST contain a targetNamespace
attribute information item on its xs:schema element information item.
+
+#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-1073 = The element ''{0}'' has already been defined in another inline
XML Schema with the target namespace ''{1}''.
+Schema-1073.assertion = A WSDL 2.0 document MUST NOT define the same element
or type in more than one inlined schema.
+
+Schema-1073b = The type ''{0}'' has already been defined in another inline XML
Schema with the target namespace ''{1}''.
+Schema-1073b.assertion = A WSDL 2.0 document MUST NOT define the same element
or type in more than one inlined schema.
+
+Schema-1075 = The alternative schema language makes use of the XML Schema
namespace.
+Schema-1075.assertion = A specification of extension syntax for an alternative
schema language MUST use a namespace that is different than the namespace of
XML Schema.
+
+Schema-1079 = The binding ''{0}'' specified is not consistent with the
interface ''{1}'' specified. The binding must refer to the same interface as is
specified by the interace attribute.
+Schema-1079.assertion = If wsdlx:interface and wsdlx:binding 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 of the service or
the binding refers to no interface.
+
+Schema-1070 = The imported XML Schema is not defined with the namespace
''{0}'' that is specified on the import element.
+Schema-1070.assertion = The value of the targetNamespace attribute information
item of the xs:schema element information item of an imported schema MUST equal
the value of the namespace of the import element information item in the
importing WSDL 2.0 document.
+
+Schema-1076 = The namespace ''{0}'' specified is not an absolute IRI.
+Schema-1076.assertion = The namespace used for an alternate schema language
MUST be an absolute IRI.
+
+Types-1074 = The alternate schema language does not include a declaration of
an element information item to appear as a child of the types element.
+Types-1074.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).
+
+
+# ---------------- WSDL Component Level Assertions -------------------
+
+# If a Binding component specifies any operation-specific binding details (by
including Binding Operation components) or any fault binding details (by
including Binding Fault components) then it MUST specify an interface the
Binding component applies to, so as to indicate which interface the operations
come from.
+Binding-1044 = 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.
+
+# A Binding component that defines bindings for an Interface component MUST
define bindings for all the operations of that Interface component.
+Binding-1045 = The binding ''{0}'' does not define bindings for the interface
operation ''{1}''. When a binding specifies an interface it must specify
bindings for all of the interface's operations.
+
+# This xs:anyURI MUST be an absolute IRI as defined by [IETF RFC 3987].
+Binding-1048 = The type ''{0}'' specified for this binding is not an absolute
IRI. The type must be absolute.
+
+# For each Binding component in the {bindings} property of a Description
component, the {name} property MUST be unique.
+Binding-1049 = A binding with the name ''{0}'' has already been defined for
the description component. All bindings defined in the description component
must have unique names.
+
+# For each Binding Fault component in the {binding faults} property of a
Binding component, the {interface fault} property MUST be unique.
+BindingFault-1050 = 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.
+
+# For each Binding Fault Reference component in the {binding fault references}
property of a Binding Operation component, the {interface fault reference}
property MUST be unique.
+BindingFaultReference-1055 = A binding fault reference has already been
specified for the interface fault reference ''{0}''. Each binding fault
reference within a binding operation component must specify a unique interface
fault reference.
+
+# There MUST be an Interface Fault Reference component in the {interface fault
references} of the Interface Operation being bound with {message label} equal
to the effective message label and with {interface fault} equal to an Interface
Fault component with {name} equal to the actual value of the ref attribute
information item.
+BindingFaultReference-1059 = The binding fault reference must reference an
defined interface fault reference.
+
+# For each Binding Message Reference component in the {binding message
references} property of a Binding Operation component, the {interface message
reference} property MUST be unique.
+BindingMessageReference-1052 = A binding message reference has already been
specified for the interface message reference ''{0}''. Each binding message
reference within a binding operation component must specify a unique interface
message reference.
+
+# For each Binding Operation component in the {binding operations} property of
a Binding component, the {interface operation} property MUST be unique.
+BindingOperation-1051 = A binding operation has already been specified for the
interface operation ''{0}''. Each binding operation within a binding component
must specify a unique interface operation.
+
+Description-0024 =
+Description-0024.ref = 2.1.2
+Description-0024.assertion = Each WSDL 2.0 or type system component MUST be
uniquely identified by its qualified name.
+
+# This xs:anyURI MUST be an absolute IRI as defined by [IETF RFC 3987].
+Endpoint-1061 = The address ''{0}'' specified for this endpoint is not an
absolute IRI. The address must be absolute.
+
+# For each Endpoint component in the {endpoints} property of a Service
component, the {binding} property MUST either be a Binding component with an
unspecified {interface} property or a Binding component with an {interface}
property equal to the {interface} property of the Service component.
+Endpoint-1062 = The binding ''{0}'' specified for this endpoint specifies the
interface ''{1}'' and not the interface ''{2}'' specified by the service. The
binding specified for this endpoint must either not specify an interface or
specify the same interface as the service.
+
+Interface-1009 = This interface extends itself via the extended interface
''{0}''. An interface cannot appear in the list of interfaces it extends.
+Interface-1009.ref = 2.2.1
+Interface-1009.assertion = To avoid circular definitions, an interface MUST
NOT appear as an element of the set of interfaces it extends, either directly
or indirectly.
+
+Interface-1010 = An interface with the name ''{0}'' has already been defined
for the description component. All interfaces defined in the description
component must have unique names.
+Interface-1010.ref = 2.2.1
+Interface-1010.assertion = For each Interface component in the {interfaces}
property of a Description component, the {name} property MUST be unique.
+
+InterfaceFault-1015 =
+InterfaceFault-1015.ref = 2.3.1
+InterfaceFault-1015.assertion = In cases where, due to an interface extending
one or more other interfaces, two or more Interface Fault components have the
same value for their {name} property, then the component models of those
Interface Fault components MUST be equivalent (see 2.17 Equivalence of
Components).
+
+InterfaceFaultReference-1037 =
+InterfaceFaultReference-1037.ref = 2.6.1
+InterfaceFaultReference-1037.assertion = The value of this property MUST match
the name of a placeholder message defined by the message exchange pattern.
+
+InterfaceFaultReference-1038 =
+InterfaceFaultReference-1038.ref = 2.6.1
+InterfaceFaultReference-1038.assertion = The direction MUST be consistent with
the direction implied by the fault propagation ruleset used in the message
exchange pattern of the operation.
+
+InterfaceFaultReference-1039 = An interface fault reference with for the fault
''{0}'' and message label ''{1}'' has already been defined for this interface
operation. Each fault reference in an interface operation must have a unique
combination of fault and message label.
+InterfaceFaultReference-1039.ref = 2.6.1
+InterfaceFaultReference-1039.assertion = For each Interface Fault Reference
component in the {interface fault references} property of an Interface
Operation component, the combination of its {interface fault} and {message
label} properties MUST be unique.
+
+InterfaceMessageReference-1026 =
+InterfaceMessageReference-1026.ref = 2.5.1
+InterfaceMessageReference-1026.assertion = The direction MUST be the same as
the direction of the message identified by the {message label} property in the
{message exchange pattern} of the Interface Operation component this is
contained within.
+
+InterfaceMessageReference-1028 = The message content model is #any or #none
and the element declaration is not empty. The element declaration must be empty
when the message content model is #any or #none.
+InterfaceMessageReference-1028.ref = 2.5.1
+InterfaceMessageReference-1028.assertion = When the {message content model}
property has the value #any or #none the {element declaration} property MUST be
empty.
+
+InterfaceMessageReference-1029 = An interface message reference with the
message label ''{0}'' has already been defined. An interface message reference
must have a unique message label within the interface operation that contains
it.
+InterfaceMessageReference-1029.ref = 2.5.1
+InterfaceMessageReference-1029.assertion = For each Interface Message
Reference component in the {interface message references} property of an
Interface Operation component, its {message label} property MUST be unique.
+
+InterfaceOperation-20970 =
+InterfaceOperation-20970 = 2.4.1
+InterfaceOperation-20970.assertion = In cases where, due to an interface
extending one or more other interfaces, two or more Interface Operation
components have the same value for their {name} property, then the component
models of those Interface Operation components MUST be equivalent (see 2.17
Equivalence of Components).
+
+InterfaceOperation-20973 =
+InterfaceOperation-20973.ref = 2.4.1.2
+InterfaceOperation-20973.assertion = An Interface Operation component MUST
satisfy the specification defined by each operation style identified by its
{style} property.
+
+MEP-1022 = The message exchange pattern ''{0}'' is not absolute. A message
exchange pattern must be identified by an absolute IRI.
+MEP-1022.ref = 2.4.1.1
+MEP-1022.assertion = A message exchange pattern is uniquely identified by an
absolute IRI which is used as the value of the {message exchange pattern}
property the Interface Operation component, and it specifies the fault
propagation ruleset that its faults obey.
+
+MessageLabel-1024 =
+MessageLabel-1024.ref = 2.5.1
+MessageLabel-1024.assertion = The value of this property MUST match the name
of a placeholder message defined by the message exchange pattern.
+
+QName-0002 =
+QName-0002.assertion = Furthermore, all QName references, whether to the same
of to difference namespace MUST resolve to components (see 2.1.9 QName
resolution).
+
+# For each Service component in the {services} property of a Description
component, the {name} property MUST be unique.
+Service-1060 = A service with the name ''{0}'' has already been defined for
the description component. All services defined in the description component
must have unique names.
+
+Types-1008 =
+Types-1008.ref = 2.1.2.1
+Types-1008.assertion = It is an error if there are multiple type definitions
for each QName.
+
+# ------------SECTION 3: WSDL-related warnings -------------------
+# These warnings were pulled from the WSDL 2.0 spec and are possible warnings
+# for the validator to report.
+
+Description-S0001 =
+Description-S0001.ref = 2.1.2
+Description-S0001.assertion = The value of the targetNamespace attribute
information item SHOULD be a dereferenceable IRI (see [IETF RFC 3987])
+
+InterfaceFault-S0002 =
+InterfaceFault-S0002.ref = 2.3.1
+InterfaceFault-S0002.assertion = For the above reason, it is considered good
practice to ensure, where necessary, that the local name of the {name} property
of Interface Fault components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
+
+InterfaceOperation-S0003 =
+InterfaceOperation-S0003.ref = 2.4.1
+InterfaceOperation-S0003.assertion = For the above reason, it is considered
good practice to ensure, where necessary, that the {name} property of Interface
Operation components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
+
------------------- End of Messages ----------------------------
Propchange:
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
------------------------------------------------------------------------------
svn:eol-style = native
Modified:
incubator/woden/trunk/java/src/org/apache/woden/internal/OMWSDLFactory.java
URL:
http://svn.apache.org/viewvc/incubator/woden/trunk/java/src/org/apache/woden/internal/OMWSDLFactory.java?rev=568932&r1=568931&r2=568932&view=diff
==============================================================================
--- incubator/woden/trunk/java/src/org/apache/woden/internal/OMWSDLFactory.java
(original)
+++ incubator/woden/trunk/java/src/org/apache/woden/internal/OMWSDLFactory.java
Thu Aug 23 04:01:23 2007
@@ -1,50 +1,50 @@
-/**
+/**
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.woden.internal;
-
-import org.apache.woden.WSDLException;
-import org.apache.woden.WSDLFactory;
-import org.apache.woden.WSDLReader;
-import org.apache.woden.internal.wsdl20.DescriptionImpl;
-import org.apache.woden.internal.wsdl20.extensions.PopulatedExtensionRegistry;
-import org.apache.woden.wsdl20.extensions.ExtensionRegistry;
-import org.apache.woden.wsdl20.xml.DescriptionElement;
-
-public class OMWSDLFactory extends WSDLFactory {
-
- private WSDLContext fWsdlContext;
-
- public OMWSDLFactory() throws WSDLException {
- fWsdlContext = new WSDLContext(this, new ErrorReporterImpl());
- ExtensionRegistry extReg = newPopulatedExtensionRegistry();
- fWsdlContext.setExtensionRegistry(extReg);
- }
-
- //Returns an OMWSDLReader
- public WSDLReader newWSDLReader() throws WSDLException {
- return new OMWSDLReader(fWsdlContext);
- }
-
- public DescriptionElement newDescription() {
- return new DescriptionImpl(fWsdlContext);
- }
-
- public ExtensionRegistry newPopulatedExtensionRegistry() {
- return new PopulatedExtensionRegistry(fWsdlContext);
- }
-
-}
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.woden.internal;
+
+import org.apache.woden.WSDLException;
+import org.apache.woden.WSDLFactory;
+import org.apache.woden.WSDLReader;
+import org.apache.woden.internal.wsdl20.DescriptionImpl;
+import org.apache.woden.internal.wsdl20.extensions.PopulatedExtensionRegistry;
+import org.apache.woden.wsdl20.extensions.ExtensionRegistry;
+import org.apache.woden.wsdl20.xml.DescriptionElement;
+
+public class OMWSDLFactory extends WSDLFactory {
+
+ private WSDLContext fWsdlContext;
+
+ public OMWSDLFactory() throws WSDLException {
+ fWsdlContext = new WSDLContext(this, new ErrorReporterImpl());
+ ExtensionRegistry extReg = newPopulatedExtensionRegistry();
+ fWsdlContext.setExtensionRegistry(extReg);
+ }
+
+ //Returns an OMWSDLReader
+ public WSDLReader newWSDLReader() throws WSDLException {
+ return new OMWSDLReader(fWsdlContext);
+ }
+
+ public DescriptionElement newDescription() {
+ return new DescriptionImpl(fWsdlContext);
+ }
+
+ public ExtensionRegistry newPopulatedExtensionRegistry() {
+ return new PopulatedExtensionRegistry(fWsdlContext);
+ }
+
+}
Propchange:
incubator/woden/trunk/java/src/org/apache/woden/internal/OMWSDLFactory.java
------------------------------------------------------------------------------
svn:eol-style = native
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
