>> Also can someone provide a WSDL for the AXIS samples/message/MessageService.java? >> The one generated by AXIS seems not right. It still indicates as rpc style call and use soap encoding instead of literal.
I'm not seeing that with AXIS1.1beta - the generated WSDL for that service says doc/literal (see below). <?xml version="1.0" encoding="UTF-8" ?> - <wsdl:definitions targetNamespace="http://mburati02.bowstreet.com:7001/bowstreet/services/Mess ageService" xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://mburati02.bowstreet.com:7001/bowstreet/services/MessageSe rvice" xmlns:intf="http://mburati02.bowstreet.com:7001/bowstreet/services/MessageSe rvice" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tns1="" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> - <wsdl:types> - <schema targetNamespace="" xmlns="http://www.w3.org/2001/XMLSchema";> <import namespace="http://schemas.xmlsoap.org/soap/encoding/"; /> <element name="echoElementsReturn" type="xsd:anyType" /> </schema> </wsdl:types> <wsdl:message name="echoElementsRequest" /> - <wsdl:message name="echoElementsResponse"> <wsdl:part element="echoElementsReturn" name="echoElementsReturn" /> </wsdl:message> - <wsdl:portType name="MessageService"> - <wsdl:operation name="echoElements"> <wsdl:input message="impl:echoElementsRequest" name="echoElementsRequest" /> <wsdl:output message="impl:echoElementsResponse" name="echoElementsResponse" /> </wsdl:operation> </wsdl:portType> - <wsdl:binding name="MessageServiceSoapBinding" type="impl:MessageService"> <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"; /> - <wsdl:operation name="echoElements"> <wsdlsoap:operation soapAction="" /> - <wsdl:input name="echoElementsRequest"> <wsdlsoap:body namespace="http://mburati02.bowstreet.com:7001/bowstreet/services/MessageSer vice" use="literal" /> </wsdl:input> - <wsdl:output name="echoElementsResponse"> <wsdlsoap:body namespace="http://mburati02.bowstreet.com:7001/bowstreet/services/MessageSer vice" use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> - <wsdl:service name="MessageService"> - <wsdl:port binding="impl:MessageServiceSoapBinding" name="MessageService"> <wsdlsoap:address location="http://mburati02.bowstreet.com:7001/bowstreet/services/MessageServ ice" /> </wsdl:port> </wsdl:service> </wsdl:definitions> -----Original Message----- From: Kevin Zico [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 8:55 AM To: [EMAIL PROTECTED] Subject: AXIS interop question on Message Services If I crete a Message style Service with AXIS. (Which implement an interface of "Element[] method(Element[])") Will .NET or other WS implementation be able to generate a client for this service? Also can someone provide a WSDL for the AXIS samples/message/MessageService.java? The one generated by AXIS seems not right. It still indicates as rpc style call and use soap encoding instead of literal. Thanks in advance. -Kev __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
