On Friday 12 November 2010 4:08:16 pm Ron Wheeler wrote: > On 12/11/2010 3:52 PM, Daniel Kulp wrote: > > On Wednesday 10 November 2010 2:48:08 pm Ron Wheeler wrote: > >> The following WSDL is used to build clients for a major conferencing > >> site. It fails validation in CXF's wsdl2java program but will work in > >> Axis. > >> > >> We are heavy users of CXF, so we are a bit disappointed that we have to > >> pick Tup another tool. > >> > >> Any ideas about why this will not validate? > >> This operation is duplicated several times which is what we think might > >> be at the root of the problem. > >> > >> <wsdl:operation name="Add"> > >> Any idea about why this is a problem for CXF but works with Axis? > > > > Well, that WSDL is not WS-I Basic Profile compliant. Thus, pretty much > > by definition, it's not considered something that is interopable between > > stacks. > > > > Specifically: > > http://www.ws-i.org/profiles/basicprofile-1.1.html#Distinctive_Operations > > > > Operation name overloading in a wsdl:portType is disallowed by the > > Profile. R2304 A wsdl:portType in a DESCRIPTION MUST have operations > > with distinct values for their name attributes. > > Thanks. > This is a very good description that I can pass on to the service > provider and see if they want to change this. > > We were able to get this working with Axis so we are OK to finish our > client but I would rather have stayed with CXF.
Just for your information, it also doesn't work with the JAX-WS reference implementation. -- Daniel Kulp [email protected] http://dankulp.com/blog
