Re: Interface Operation Name

Menon,,

There is no contradiction here. The component model creates the Operation 
QName by combining the NCName specified by the name attribute of the 
<operation> with the URI specified by the targetNamespace attribute of the 
enclosing <description> element. This is the way that XML Schema works 
too, e.g. for <element> and <complexType>.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



Ramkumar Menon <ramkumar.menon@gmail.com> 
Sent by: www-ws-desc-request@w3.org
02/14/2006 08:47 AM

To
www-ws-desc@w3.org
cc

Subject
Re: Interface Operation Name






FYI, the XML representation is available in section 2.4.2 of the same 
specification.
-Menon

 
On 2/14/06, Ramkumar Menon <ramkumar.menon@gmail.com> wrote: 
Hi,
 
FYI, Section 2.4.1 of WSDL 2.0 Core Language spec dicates the name 
property for the interface operation as
{name} REQUIRED. An xs:QName.
In the XML Representation, it is mentioned as an xs:NCName.
<description>
  <interface>
    <operation
          name="xs:NCName" 
          pattern="xs:anyURI"
          style="list of xs:anyURI"? >
      <documentation />*
      [ <feature /> | <property /> | 
        [ <input /> | <output /> | <infault /> | <outfault /> ]+ 
      ]*
    </operation>
  </interface>
</description>
 
 
rgds,
Menon


-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor 



-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor