Author: jkaputin
Date: Wed Jun 13 08:04:08 2007
New Revision: 546905
URL: http://svn.apache.org/viewvc?view=rev&rev=546905
Log:
WODEN-149
Removed messages for obsolete WSDL2 assertions from
the CR spec that are no longer in the PR spec.
Modified:
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
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?view=diff&rev=546905&r1=546904&r2=546905
==============================================================================
---
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
(original)
+++
incubator/woden/trunk/java/src/org/apache/woden/internal/Messages.properties
Wed Jun 13 08:04:08 2007
@@ -155,14 +155,6 @@
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.
-# This assertion is for interface message reference
-Schema-0020 = The message reference ''{0}'' refers to the type definition
''{1}''. A message reference must refer to an element definition.
-Schema-0020.assertion = An element attribute information item MUST NOT refer
to a global xs:simpleType or xs:complexType definition.
-
-# This assertion is for interface fault
-Schema-0020b = The fault ''{0}'' refers to the type definition ''{1}''. A
fault must refer to an element definition.
-Schema-0020b.assertion = An element attribute information item MUST NOT refer
to a global xs:simpleType or xs:complexType definition.
-
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.
@@ -215,9 +207,6 @@
# 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 {name} property MUST be unique.
-Endpoint-0065 = A endpoint with the name ''{0}'' has already been defined for
the service component. All endpoints defined in a service component must have
unique names.
-
# 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.
@@ -229,14 +218,6 @@
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-0028 = The namespace of the interface operation name must be
the same as the namespace of the interface name.
-InterfaceFault-0028.ref = 2.2.1
-InterfaceFault-0028.assertion = The namespace name of the {name} property of
each Interface Fault in this set MUST be the same as the namespace name of the
{name} property of this Interface component.
-
-InterfaceFault-0032 = An interface fault with the name ''{0}'' has already
been defined for the interface component. All interface faults defined for an
interface component must have a unique name.
-InterfaceFault-0032.ref = 2.3.1
-InterfaceFault-0032.assertion = For each Interface Fault component in the
{interface faults} property of an Interface 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).
@@ -264,14 +245,6 @@
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-0029 = The namespace of the interface operation name must
be the same as the namespace of the interface name.
-InterfaceOperation-0029.ref = 2.2.1
-InterfaceOperation-0029.assertion = The namespace name of the {name} property
of each Interface Operation in this set MUST be the same as the namespace name
of the {name} property of this Interface component.
-
-InterfaceOperation-0035 = An interface operation with the name ''{0}'' has
already been defined for the interface component. All interface operations
defined for an interface component must have a unique name.
-InterfaceOperation-0035.ref = Section 2.4.1
-InterfaceOperation-0035.assertion = For each Interface Operation component in
the {interface operations} property of an Interface component, the {name}
property MUST be unique.
InterfaceOperation-20970 =
InterfaceOperation-20970 = 2.4.1
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
