I prefer the current Metro/CXF default. Header parameters are usually
the same and duplicated on all methods in a class. When my eyes are
scrolling across a method signature line I like to see the
method-specific parameters first and ignore the boilerplate header
fields at the end instead of needing to wade through the latter every
time before I can get to the unique method-specific stuff I'm interested in.
Glen
On 11/01/2012 08:16 AM, timis wrote:
Glen,
Thank you for your quick reply.
Metro wsdl
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<definitions targetNamespace="http://foo.test.com/"; name="FooService"
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsp="http://www.w3.org/ns/ws-policy"; xmlns:tns="http://foo.test.com/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
<types>
<xsd:schema>
<xsd:import namespace="http://foo.test.com/";
schemaLocation="FooService_schema1.xsd"/>
</xsd:schema>
</types>
<message name="getFoo">
<part name="parameters" element="tns:getFoo"/>
<part name="context" element="tns:context"/>
</message>
<message name="getFooResponse">
<part name="result" element="tns:getFooResponse"/>
</message>
<portType name="Foo">
<operation name="getFoo" parameterOrder="parameters context">
<input wsam:Action="http://foo.test.com/Foo/getFooRequest";
message="tns:getFoo"/>
<output wsam:Action="http://foo.test.com/Foo/getFooResponse";
message="tns:getFooResponse"/>
</operation>
</portType>
<binding name="FooPortBinding" type="tns:Foo">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http";
style="document"/>
<operation name="getFoo">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" parts="parameters"/>
<soap:header message="tns:getFoo" part="context" use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="FooService">
<port name="FooPort" binding="tns:FooPortBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
As you can see order of parameters has changed, but I didn't find anything
about it in the wsdl specification. I wish I had the same SEI after
generation from wsdl.
--
View this message in context:
http://cxf.547215.n5.nabble.com/WebParam-header-true-and-it-s-place-in-generated-SEI-tp5717680p5717689.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
