Both programming models create a SOAP message and send it to the service endpoint. The first method gives you more explicit control over the interaction, and it supports more dynamic capabilities. The second method is more automatic, but less dynamic. You can choose your method based on your programming preferences and your application requirements.
One reason why you may have had trouble with the XI service is that you may not have set all the necessary settings properly. One advantage of using a compiled stub is that you can depend on Axis to set all the necessary settings properly (as specified in the WSDL). Here's a tutorial using a compiled stub: http://ws.apache.org/axis/cpp/arch/End-2-End-Sample.html Anne On 9/6/06, Chris Riekenberg <[EMAIL PROTECTED]> wrote:
Hi, I'm new with web services in java an got an understanding problem. There are two types for consuming a web service: 1) Call a service direct Service service = new Service(); Call call = (Call)service.createCall(); ... String ret = (String)call.invoke(params); 2) Consuming a WSDL and creating stubs MI_RFC_CALL_SYNC_OUTService serviceLocator = new MI_RFC_CALL_SYNC_OUTServiceLocator(); ... Questions: ========== 1.) When do you use which one?? I tried first way and it works good with open/free web services, but it failed with a web service of SAP XI. 2.) In first way, the WSDL-File isn't needed, is it? I only need information out of it, but it's binded nowhere, right? 3.) Did anyone got a good example for the second way? I read the user's guide of apache, but got problems with it. thanks christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
