web-dev-qa-db-fra.com

Comment appeler un service WCF utilisant ksoap2 sur Android?

Voici mon code

import org.ksoap2.*;
import org.ksoap2.serialization.*;
import org.ksoap2.transport.*;

import Android.app.Activity;
import Android.os.Bundle;
import Android.widget.TextView;

public class ksop2test extends Activity {
 /** Called when the activity is first created. */


 private static final String METHOD_NAME = "SayHello";
// private static final String METHOD_NAME = "HelloWorld";

 private static final String NAMESPACE = "http://tempuri.org";
// private static final String NAMESPACE = "http://tempuri.org";

 private static final String URL = "http://192.168.0.2:8080/HelloWCF/Service1.svc";
// private static final String URL = "http://192.168.0.2:8080/webservice1/Service1.asmx";

 final String SOAP_ACTION = "http://tempuri.org/IService1/SayHello";
// final String SOAP_ACTION = "http://tempuri.org/HelloWorld";
 TextView tv;
 StringBuilder sb;



 @Override
 public void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  tv = new TextView(this);
  sb = new StringBuilder();
  call();
  tv.setText(sb.toString());
  setContentView(tv);
 }

 public void call() {
  try {

   SoapObject request = new SoapObject(NAMESPACE, METHOD_NAME);

   request.addProperty("name", "Qing");

   SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(
     SoapEnvelope.VER11);
   envelope.dotNet = true;
   envelope.setOutputSoapObject(request);


   HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
   androidHttpTransport.call(SOAP_ACTION, envelope);
   sb.append(envelope.toString() + "\n");//cannot get the xml request send
   SoapPrimitive result = (SoapPrimitive)envelope.getResponse();

   //to get the data
   String resultData = result.toString();
   // 0 is the first object of data 


   sb.append(resultData + "\n");
  } catch (Exception e) {
   sb.append("Error:\n" + e.getMessage() + "\n");
  }

 }

}

Je peux accéder avec succès au service .asmx, mais lorsque j'essaie d'appeler un service wcf, la machine virtuelle dit: Erreur: attendu: END_TAG { http://schemas.xmlsoap.org/soap/envelope/ } Corps (position : END_TAGhttp: //schemas.xmlsoap.org/soap/envelope/} s: Erreur> @ 1: 712 dans Java.io.InputStreamReader@43ba6798

Comment imprimer ce que la demande envoie?

Voici le wcf wsdl:

<wsdl:definitions name="Service1" targetNamespace="http://tempuri.org/">

<wsdl:types>
  <xsd:schema targetNamespace="http://tempuri.org/Imports">
  <xsd:import schemaLocation="http://para-bj.para.local:8080/HelloWCF/Service1.svc?xsd=xsd0" namespace="http://tempuri.org/"/>
  <xsd:import schemaLocation="http://para-bj.para.local:8080/HelloWCF/Service1.svc?xsd=xsd1" namespace="http://schemas.Microsoft.com/2003/10/Serialization/"/>
  </xsd:schema>
</wsdl:types>

<wsdl:message name="IService1_SayHello_InputMessage">
  <wsdl:part name="parameters" element="tns:SayHello"/>
</wsdl:message>

<wsdl:message name="IService1_SayHello_OutputMessage">
  <wsdl:part name="parameters" element="tns:SayHelloResponse"/>
</wsdl:message>

<wsdl:portType name="IService1">
  <wsdl:operation name="SayHello">
    <wsdl:input wsaw:Action="http://tempuri.org/IService1/SayHello" message="tns:IService1_SayHello_InputMessage"/>
    <wsdl:output wsaw:Action="http://tempuri.org/IService1/SayHelloResponse" message="tns:IService1_SayHello_OutputMessage"/>
  </wsdl:operation>
</wsdl:portType>

<wsdl:binding name="BasicHttpBinding_IService1" type="tns:IService1">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>

  <wsdl:operation name="SayHello">
   <soap:operation soapAction="http://tempuri.org/IService1/SayHello" style="document"/>

     <wsdl:input>
       <soap:body use="literal"/>
     </wsdl:input> 
     <wsdl:output>
       <soap:body use="literal"/>
     </wsdl:output>
  </wsdl:operation>
</wsdl:binding>

<wsdl:service name="Service1">

  <wsdl:port name="BasicHttpBinding_IService1" binding="tns:BasicHttpBinding_IService1">
    <soap:address location="http://para-bj.para.local:8080/HelloWCF/Service1.svc"/>
  </wsdl:port>
</wsdl:service>

</wsdl:definitions>

Il utilise <xsd:schema> dans la balise <wsdl:types> et le asmx utilise <s:schema> dans la balise <wsdl:types> quelle est la différence?

androidwcfksoap2
18
Qing

enfin je l'ai fait fonctionner parce que l'espace de noms manquait un "/" à la fin,

ce qui suit est mon code

package cn.qing.ksop2test;


import Java.io.Writer;

import org.ksoap2.*;
import org.ksoap2.serialization.*;
import org.ksoap2.transport.*;
import org.xmlpull.v1.XmlSerializer;

import Android.app.Activity;
import Android.os.Bundle;
import Android.util.Xml;
import Android.widget.TextView;

public class ksop2test extends Activity {
/** Called when the activity is first created. */


private static final String METHOD_NAME = "HelloWorldRequest";
//  private static final String METHOD_NAME = "HelloWorld";

private static final String NAMESPACE = "http://tempuri.org/";
//  private static final String NAMESPACE = "http://tempuri.org";

private static final String URL = "http://192.168.0.2:8080/HelloWCF/Service1.svc";
//  private static final String URL = "http://192.168.0.2:8080/webservice1  /Service1.asmx";

final String SOAP_ACTION = "http://tempuri.org/IService1/HelloWorld";
//  final String SOAP_ACTION = "http://tempuri.org/HelloWorld";
TextView tv;
StringBuilder sb;
private XmlSerializer writer;



@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    tv = new TextView(this);
    sb = new StringBuilder();
    call();
    tv.setText(sb.toString());
    setContentView(tv);
}

public void call() {
    try {

        SoapObject request = new SoapObject(NAMESPACE, METHOD_NAME);

        request.addProperty("Name", "Qing");

        SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(
                SoapEnvelope.VER11);
        envelope.dotNet = true;
        envelope.setOutputSoapObject(request);


        HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
        androidHttpTransport.call(SOAP_ACTION, envelope);
        SoapPrimitive result = (SoapPrimitive)envelope.getResponse();

        //to get the data
        String resultData = result.toString();
        // 0 is the first object of data 


        sb.append(resultData + "\n");
        } catch (Exception e) {
        sb.append("Error:\n" + e.getMessage() + "\n");
        }

    }

}
19
Qing

J'utilise

private static final String SOAP_ACTION = "http://tempuri.org/IContact/GetContactCount";
private static final String METHOD_NAME = "GetContactCount";
private static final String NAMESPACE = "http://tempuri.org/";
private static final String URL = "http://xxx.xxx.com/Contacts/ContactsService.Contacts.svc";

Alors peut-être que le problème réside dans votre action SOAP.

De plus, l'orthographe sur le nom de votre méthode est-elle correcte, à savoir AuthenticatdUser?

1
Leo Moore

Merci Qing pour votre réponse, c'est vraiment une aide complète pour appeler le service WCF

Je voudrais ajouter cette rectification pour obtenir une sortie simple et complexe d'un service Web après avoir défini outputSoapObject dans une enveloppe, corrigez-moi si je me trompe.

envelope.setOutputSoapObject(requestSoapObject);

        // if its dotnet web service then make it true
        if (isDotNetWebService)
            envelope.dotNet = true;

        HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
        androidHttpTransport.call(NAMESPACE + methodName, envelope);

        if (useBodyIn) // use bodyIn if service method returns string/int
                        // etc
        {
            /* Gives output from webservice */
            responseSoapObject = (SoapObject) envelope.bodyIn;
        } else // use getResponse() if service method returns objects or
                // array
        {
            /* Gives output from webservice */
            responseSoapObject = (SoapObject) envelope.getResponse();
        }
0
Neelam Singh

En "théorie", wcf avec une liaison HTTP de base et asmx devrait fonctionner de la même manière.

Cela pourrait être lié à la configuration de votre service WCF.

Nous avons un problème similaire si nous configurons TransferMode Streamed sur le client et Buffered sur le serveur. Bien que ne sachant pas si cela est pertinent dans votre cas.

0
Shiraz Bhaiji