No need for Web Application Server Java to implement WebServices

Recently, I browsed some posts about Java to implement WebServives in the community, and found that more than 90% of them have such one operation:

In fact, this method is correct, but it kills many advantages of WebServices. So let's take a look at what is WebServices from the beginning.

Baidu encyclopedia wrote:

Web Services are online application Services released by enterprises to meet their specific business needs. Other companies or application software can access and use this online service over the Internet. It is a universal model for building applications and can be run in any operating system that supports network communication. It is a new web Application Branch, it is a self-contained, self-describing, and modular application that can be released, located, and called through the web.

Web Service is an application component that logically provides data and services for other applications. each application accesses the Web Service through the network protocol and some standard data formats Http, XML, and Soap. The results are obtained through the internal execution of the Web Service. web services can execute any function from simple requests to complex business processing. After deployment, other Web Service applications can discover and call the services deployed by the application.

The following key technologies and rules are used to build and use Web services:

1. XML: Standard Method for describing data.

2. SOAP: indicates the Information Exchange Protocol.

3. WSDL: Web Service Description Language.

4. UDDI (Universal Description, Discovery and Integration): Universal Description, Discovery, and Integration. It is a platform-independent, XML-based protocol used to describe commerce on the Internet. In fact, the main goal of WebService is cross-platform interoperability. To achieve this goal, WebService is fully based on XML eXtensible Markup Language), XSDXMLSchema, and other standards independent of platforms and software vendors, is a new platform for creating interoperable and distributed applications.

Persistent Item 1: Cross-firewall communication.

Long term 2: Application Integration.

Item 3: B2B Integration.

Back to the Title I mentioned, do WebServices really need any Jar packages? Do I need a plug-in? In fact, there are many ways to implement webservice, such as the axis framework and xfire framework, which can be used to publish the wsdl interface or implement the webservice client. Currently, eclipse has integrated plug-ins, you can generate a webservice client to call the interface according to the wsdl file. However, in this case, you must rely on the jar package of the Framework. Sometimes, due to environment and other reasons, we only need one interface in the wsdl, at this time, xml data can be directly generated through the http interface or socket interface to call the webservice Service on the server. In fact, the bottom layer of webservice still sends xml data, the framework encapsulates the serialization and deserialization of xml data. The following two simple examples describe the http and socket methods. Example 1: http webservice Interface call example:

 
 

  
  
Import java. io. BufferedReader;
  
  
Import java. io. IOException;
  
  
Import java. io. InputStreamReader;
  
  
Import java. io. OutputStreamWriter;
  
  
Import java. io. UnsupportedEncodingException;
  
  
Import java.net. MalformedURLException;
  
  
Import java.net. URL;
  
  
Import java.net. URLConnection;
  
  

  
  
Public class HttpPostTest {
  
  
Void testPost (String urlStr ){
  
  
Try {
  
  
URL url = new URL (urlStr );
  
  
URLConnection con = url. openConnection ();
  
  
Con. setDoOutput (true );
  
  
Con. setRequestProperty ("Pragma:", "no-cache ");
  
  
Con. setRequestProperty ("Cache-Control", "no-cache ");
  
  
Con. setRequestProperty ("Content-Type", "text/xml ");
  
  

  
  
OutputStreamWriter out = new OutputStreamWriter (con. getOutputStream ());
  
  
String xmlInfo = getXmlInfo ();
  
  
Out. write (new String (xmlInfo ));
  
  
Out. flush ();
  
  
Out. close ();
  
  
BufferedReader br = new BufferedReader (new InputStreamReader (con. getInputStream ()));
  
  
String line = "";
  
  
StringBuffer buf = new StringBuffer ();
  
  
For (line = br. readLine (); line! = Null; line = br. readLine ()){
  
  
Buf. append (new String (line. getBytes (), "UTF-8 "));
  
  
}
  
  
System. out. println (buf. toString ());
  
  
} Catch (MalformedURLException e ){
  
  
E. printStackTrace ();
  
  
} Catch (IOException e ){
  
  
E. printStackTrace ();
  
  
}
  
  
}
  
  

  
  
Private String getXmlInfo (){
  
  
// You can view the interface xml format data through the wsdl file to construct the xml data of the calling interface.
  
  
String xml = "<SOAP-ENV: Envelope xmlns: SOAP-ENV = \" extensions "xmlns: SOAP-ENC = \" extensions "xmlns: xsi = \" http://www.w3.org/2001/XMLSchema-instance\ "xmlns: xsd = \ "http://www.w3.org/2001/XMLSchema\">"
  
  
+ "<SOAP-ENV: Body>"
  
  
+ "<M: getItemDetailSingle xmlns: m = \" http: xxxxxxxxxxxxxxxx/\ ">"
  
  
+ "<ItemMo>"
  
  
+ "<Category> government domain name </category>"
  
  
+ "<City> beili, xiba River, Beijing </city>"
  
  
+ "<Flag> 3 </flag>"
  
  
+ "<ItemId> 10 </itemId>"
  
  
+ "<ItemIndex> 22 </itemIndex>"
  
  
+ "<Keyword> Chaoyang District </keyword>"
  
  
+ "<Mobile> 139-0111-1111 </mobile>"
  
  
+ "<Password> iteyePl </password>"
  
  
+ "<UserName> hwak </userName>"
  
  
+ "</ItemMo>"
  
  
+ "</M: getItemDetailSingle>"
  
  
+ "</SOAP-ENV: Body>"
  
  
+ "</SOAP-ENV: Envelope> ";
  
  
Return xml;
  
  
}
  
  

  
  
Public static void main (String [] args) throws UnsupportedEncodingException {
  
  
String url = "http: // localhost: 9999/dataService/services/Job ";
  
  
New HttpPostTest (). testPost (url );
  
  
}
  
  
} </PRE>
 
 

We can see from the above two examples that Web application servers are not necessary when Java is used to implement WebServices. We hope that you can make good use of the advantages provided by WebServices according to local conditions, be good at doing it!

Recommended Editing: