Glen,
When you say "I'd like to make THESE THREE the accepted APIs for message-style service methods" are you just implying these are the return and parameter signatures? Or these are THE names of methods? Is option 3 as described in http://marc.theaimsgroup.com/?l=axis-dev&m=101853538321442&w=2 similar to support we had previously except namespace sensitive? Let me illustrate a case: Pertinent WSDL: <wsdl:binding name="PhonyTrans" type="notimportant"> <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="MerchDescription"> <wsdlsoap:operation soapAction="" style="document"/> <wsdl:input> <wsdlsoap:body use="literal"/> </wsdl:input> <wsdl:output> <wsdlsoap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="POR"> <wsdlsoap:operation soapAction="" style="document"/> <wsdl:input> <wsdlsoap:body use="literal"/> </wsdl:input> <wsdl:output> <wsdlsoap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> Pertinent WSDD: <service name="mapped" style="message" provider="java:MSG"> <parameter name="allowedMethods" value="*"/> <parameter name="className" value="PhonyService"/> <operation name="MerchDescription" qname="ns:MerchDescripition" xmlns:ns="http://phony.com"/> <operation name="POR" qname="ns:POR" xmlns:ns="http://phony.com"/> </service> Pertinent Java: My class: class PhonyService{ public SOAPBodyElement [] MerchDescription(SOAPBodyElement [] bodies){...} //Parms determined by introspections public Element [] POR(Element [] bodies){..} //Parms determined by introspection } Or am I way off target here? Thanks. Rick Rineholt "The truth is out there... All you need is a better search engine!" [EMAIL PROTECTED] Glen Daniels <[EMAIL PROTECTED]> on 09/23/2002 03:14:47 PM Please respond to [EMAIL PROTECTED] To: "'Axis-Dev (E-mail)'" <[EMAIL PROTECTED]> cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> Subject: Message style services - ATTN ANY java:MSG USERS OK, I have dispatch to multiple methods in message-style services working in my sandbox. This has the added bonus of speeding up message-based services because we now avoid introspection on every call - the initial introspection in ServiceDesc now understands what type of message method (Vector, Document, etc) we have so the MsgProvider can use that cached info. While we're in there, I'd suggest rationalizing the APIs for message based backends, as discussed in http://marc.theaimsgroup.com/?l=axis-dev&m=101853538321442&w=2. (incidentally I think it's funny that I was set to do exactly this work back in April - the dispatch stuff now works pretty much exactly as in that message) I'd like to make THESE THREE the accepted APIs for message-style service methods: public class MessageService { public SOAPBodyElement [] bodyMethod(SOAPBodyElement [] bodies) public SOAPEnvelope envelopeMethod(SOAPEnvelope envelope) public Element [] bodyAsDOMMethod(Element [] bodies) } I think these make a lot more sense than what we've got now. IF THIS WILL AFFECT YOU IN A NEGATIVE WAY, or IF YOU DISAGREE WITH THESE CHANGES, please send mail to axis-dev in reply to this message. Thanks! --Glen