cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin" <>
Subject Re: Service Model problem with ws-policy
Date Tue, 05 Dec 2006 09:53:46 GMT

<wsp:PolicyReference URI="#BasicHttpBinding_IMtomTest_policy" /> is the first child
of the <binding> element, so it's placed 
correctly according to the binding schema...It references a policy with id "BasicHttpBinding_IMtomTest_policy"
located in the same 

Cheers, Sergey

Hi Andrea,

Currently, if a wsdl file contains ws-policy assertions,
our cxf can't build service model correctly.

In WSDLServiceBuilder.buildBinding method, it assumed that
the first ext element is the one specify the protocol (such
as soap), but if the wsdl has ws-policy assertion, the first
element of binding may be the wsp:PolicyReference.

our code:
String ns = ((ExtensibilityElement)binding.getExtensibilityElements()

wsdl sample:
    <wsdl:binding name="BasicHttpBinding_IMtomTest" type="i0:IMtomTest">
        <wsp:PolicyReference URI="#BasicHttpBinding_IMtomTest_policy" />
        <soap:binding transport="" />

But what make me confused is when I look up the wsdl spec
(, I found the binding chapter specify
the binding part should like below:

Digest from

The grammar for a binding is as follows:

<wsdl:definitions .... >
    <wsdl:binding name="nmtoken" type="qname"> *
        <-- extensibility element (1) --> *
        <wsdl:operation name="nmtoken"> *
           <-- extensibility element (2) --> *
           <wsdl:input name="nmtoken"? > ?
               <-- extensibility element (3) -->
           <wsdl:output name="nmtoken"? > ?
               <-- extensibility element (4) --> *
           <wsdl:fault name="nmtoken"> *
               <-- extensibility element (5) --> *

Could we add a filter out map in WSDLServiceBuilder to filter out any
well-known elements namespace which may precedes the protocol element of
the binding to solve this type problem.


View raw message