OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema

I have tried the 0.95 and the proposed changes in 0.95 with AXIS1.1RC2 and
could not find any relevant difference on the generated stubs and code,
i.e. the messages sent over the wire would be the same.
For me the change seems to be fine for consistency reasons.

However, Yossi or Claus, could you point me to WS-I basic profile
requirement stating this, I wasn't able to find this statement there. Or
point me to the statement in the WSDL schema.
What I found in the WSDL 1.1 spec for SOAP binding extensions:

<definitions .... >
    <binding .... >
        <operation .... >
               <soap:fault name="nmtoken" use="literal|encoded"
                                 encodingStyle="uri-list"? namespace

Here the name is defined as being of type NMToken not NCName. And NMToken
is defined as follows:

Names and Tokens
 [4] NameCha ::  Letter | Digit | '.' | '-' | '_' | ':' | CombiningChar   
           r  =  | Extender                                               
 [5]    Name ::  (Letter | '_' | ':') (NameChar)*                         
 [6]   Names ::  Name (S Name)*                                           
 [7] Nmtoken ::  (NameChar)+                                              
 [8] Nmtoken ::  Nmtoken (S Nmtoken)*                                     
           s  =                                                           

This would mean that our definition is conformant, right?

Mit freundlichen Gruessen / best regards,

        Richard Jacob
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com

|         |           Rich             |
|         |           Thompson/Watson/I|
|         |           BM@IBMUS         |
|         |                            |
|         |           04/22/2003 08:36 |
|         |           PM               |
  |                                                                                                                                                  |
  |       To:       wsrp@lists.oasis-open.org                                                                                                        |
  |       cc:                                                                                                                                        |
  |       Subject:  Re: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema                                                               |

The axis tools I have installed on my machine are able to process the
binding file with these removed. How about other tools?

Rich Thompson

   "Tamari, Yossi"                                                        
   <yossi.tamari@sap.com>            To:                                  
   04/22/2003 01:53 PM               cc:                                  
                                     Subject:        [wsrp] WSRP WSDL not 
                             currently conformant with WSDL 1.1 schema    

Claus Von Riegen, who is a new observer of the WSRP from SAP and a WSDL and
UDDI expert, had been running our WSDL through WS-I testing tools, which
check for WSDL schema conformance. He found one minor problem regarding our
definition of SOAP faults.
Our WSDL uses qualified names to reference portType fault operations from
soap:fault elements. Taking the following WSDL fragment (that is part of a
wsdl:operation, which in turn is part of a wsdl:binding) as an example,
 <wsdl:fault name="AccessDenied">
   <soap:fault name="intf:AccessDenied" use="literal"/>
The "intf:" prefix makes the WSDL document invalid against the WSDL 1.1
schema, since the soap:fault name attribute is of type NCName.

Removing all occurrences of the "intf:" prefix should resolve the issue.

I am sorry to raise this issue at such a late point, but I think that since
fixing it is very simple and should not create controversy, and since it
doesn't affect the spec itself, we can fix it without reopening the


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]