The format of the Webservice transfer command

Isn't it just a text in itself, and a string argument is fine?

2.The contents of the XML file are encoded in base64 and then transferred as byte parameters.

3.Another way is to use saaj to transfer the contents of the file as attachments in a soap package. But this doesn't seem to be a webserviece.

Which JSON library are you using? SonObject's full qualified name is posted to see.

1.Regarding the compilation fails, it's clear that jsonobject doesn't have such a constructor.

jsonobject jsonobj = new jsonobject(json);

Change to: jsonobject jsonobj = new jsonobject();

name","reiz");

Delete this line: string json ="";

2.What webservice runtime environment do you use for that service? What does it look like is the dopost doget inside the servlet?

Do you think that writing a doservice in a servlet is writing a webservice?

public void doservice(httpservletrequest request, httpservletresponse response) throws ioexception

First of all, we need to determine the encoding of the passed XMLDATA, let's say it's UTF-8.

string xmlstr = new string(xmldata, "utf-8");

After converting it to a string, you can create an XML document, and then parse the tag and put it into the database.

It feels like you should declare xmldata as a string in the interface.

WebService communicates via the SOAP protocol (Simple Object Access Collaboration), which in short, transmits XML text over HTTP. WebService defines a standard called WSDL (Web Service Definition Language), which is actually XML text, which defines the method name, parameter name, and return value information that you want to access the other server's server, but if you want to communicate with the server, you are not allowed to go through an engine called axis, which is responsible for converting objects to XML text and transmitting it to the server, and then converting XML into objects to the server, because objects on different platforms are not known to each other.

The technical architecture of WebService is relatively simple, so it is easier to learn, but it is XML text that is transmitted, so it is relatively slow.

Corba is different, it's a teleportation binary, and it's fast. But the programming model is too complex to learn. Corba is a heavyweight.

XML format, refers to data transmission, there are many data transfer formats, collections, addresses, XML transmission, etc.! This is called an interface!

To call someone else's WS

Second: You can access the WSDL URL it gives you, which means that you can call the other party's WS.

Thirdly, use the client or proxy it produces to call the other party's WS. It is based on the specific file format it gives (like xml file).

WebService opens a socket service.

Then use the socket to deal with it.

With the framework, CFX and Axis can be, search on the Internet, it's very simple, use the corresponding plug-in of Eclipse to automatically generate calls**, and then you can write**call the call just generated**, you can achieve it.

This is the general usage of webservice, please refer to it.

Actually, the first thing you need to understand about this question is XML. In fact, XML files are essentially large strings, but they are a labeled storage method. Similar to it, such as JSON, is the same, essentially a string.

It's just that this particular string has its own way of organization, and it can be restored to data by parsing.

So, the next question is why use XML instead of passing strings directly?

When strings are passed, the readability of the data will be very poor, and the function will be single. For example, an array and a list, how do you write it when you use http to pass the value?

In addition, there are many rules and specifications for XML tags, but in fact, they are all written about one thing, that is, how to organize the data you want to transmit. Its function is very similar to the serialization of classes. Serialization of classes is the transformation of entity data in the heap and stack into serialized data (which can be understood as strings).

When we write XML, we organize the materialized data we want into XML form, and then the program reads the XML and restores it to the materialized data.

Well, I have said a lot, and I have some understanding.

WebService can only transfer serialized data, and XML is preferred due to cross-platform applications.

This is the specification, and it can also be JSON or whatever.

XML is the format in which most network parameters are passed.

In ajax define the return data type, datatype:'json'to return the JSON data format in the webservice, which should return the HMTL format by default.