Skip to main content

How to parse a SoapObject in android



I'm using webservices for an application to get the data from external servers. I'm able to connect to the server, send my SOAP request and able get the data back to my android class as SoapObject. Here I'm having trouble parsing this SoapObject to retrieve the values (as strings) coming from the webservice. My code is here:







public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.list);

mInflater = (LayoutInflater)getSystemService(Activity.LAYOUT_INFLATER_SERVICE);

System.out.println("Entered "+getClass().getSimpleName());

//Calling the web service to get the documents list

callService("getDocumentsList","http://wservice.friedmaggy.com/getDocumentsList");







-- I have created callService method to call the webservice.:







public void callService(String operation, String soapaction)

{

try {

String SOAP_ACTION = soapaction;

String OPERATION_NAME = operation;

String WSDL_TARGET_NAMESPACE = getString(R.string.targetNamespace);

String SOAP_ADDRESS = getString(R.string.soapAddress);

SoapObject request = new SoapObject(

WSDL_TARGET_NAMESPACE, OPERATION_NAME);

System.out.println("SOAP_ACTION "+SOAP_ACTION);

System.out.println("OPERATION_NAME "+OPERATION_NAME);

System.out.println("WSDL_TARGET_NAMESPACE "+WSDL_TARGET_NAMESPACE);

System.out.println("SOAP_ADDRESS "+SOAP_ADDRESS);

// System.out.println("SOAP_ACTION "+SOAP_ACTION);



PropertyInfo propInfo = new PropertyInfo();



SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(

SoapEnvelope.VER11);



HttpTransportSE httpTransport = new HttpTransportSE(

SOAP_ADDRESS);

envelope.setOutputSoapObject(request);



httpTransport.call(SOAP_ACTION, envelope);



SoapObject response = (SoapObject) envelope.bodyIn;





if(response.getPropertyCount()>0){

data=new StringBuilder();



for (int i = 0; i < response.getPropertyCount(); i++) {



Course c = new Course((SoapObject) response.getProperty(i));



courseList.add(c);



}



for (Course c : courseList) {



data.append("CourseName :" + c.getName());



results.add(c.getName());

}







-- As seen above, i'm passing the whole response object to another bean class to fetch the values.(Course c = new Course((SoapObject) response.getProperty(i));)





Can you help me how to parse this response object to fetch the required String values out.?


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex