Hi Max, After reading your article I made sure that the message parts had different names in their definitions and used them for overloading the same WSDL method: getModel(). The WSDL bindings for the method uses the different message parts as appropriate.
Here is the binding generated by Java2WSDL. It shows that the input and outputs refer to different message names: | <wsdl:operation name="getModel"> | | <wsdlsoap:operation soapAction=""/> | | <wsdl:input name="getModelRequest"> | | <wsdlsoap:body namespace="http://url.com"; use="literal"/> | | </wsdl:input> | | <wsdl:output name="getModelResponse"> | | <wsdlsoap:body namespace="http://url.com"; use="literal"/> | | </wsdl:output> | | </wsdl:operation> | | <wsdl:operation name="getModel"> | | <wsdlsoap:operation soapAction=""/> | | <wsdl:input name="getModelRequest1"> | | <wsdlsoap:body namespace="http://url.com"; use="literal"/> | | </wsdl:input> | | <wsdl:output name="getModelResponse1"> | | <wsdlsoap:body namespace="http://url.com"; use="literal"/> | | </wsdl:output> | | </wsdl:operation> | JBoss WS deployer just doesn't like duplicate operation names, it seems. Your articles points out that WSDL 1.2 dropped method overloading and WS-I Basic Profile 1.0 has no method overloading. Am I trying to do something here that cannot be achieved in JBossWS? Any ideas? Claire. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882862#3882862 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882862 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
