Getting Started with Xfire

POJO, SOA overview

The POJO of being re-examined

POJO (Plain old Java object, simple Java objects) is the earliest member of the Java Community (recall the first exciting moment when you were learning Java, the simple "Hello world! Example) is also the simplest and easiest way to implement it.

However, the development of Java in reality is far beyond the scope of POJO, becoming the most successful programming language in object-oriented technology applications, especially the application of inheritance and polymorphism, has created a large number of development frameworks (such as Struts) and standards (such as EJB), followed by the complexity of implementation, We have to deal with a lot of restrictions on succession relationships. For example, to develop an application based on struts, we must understand struts-specific inheritance relationships such as actionform and validateactionform; to develop an EJB application, we must inherit Ejbobject, SESSIONEJB, and so on.

To put aside these constraints and reduce the difficulty of implementing Java applications, the Java community is beginning to re-examine the value of POJO, trying to POJO the ultimate, and the latest effort is EJB3.0. The Java community has designed EJB3.0 to be based on POJO, rather than preparing them for more inheritance relationships.

A love-hate SOA

SOA has become a hot noun in the current Java community, where almost all software vendors are talking about it, providing solutions and product support, and most businesses are already implementing or considering implementing SOA within the enterprise.

However, SOA implementation in the enterprise is not a simple task, even if the new system is directly based on the implementation of the SOA architecture, it is not easy to integrate enterprise systems into the SOA framework. In order to meet the new requirements, the enterprise must make a large-scale transformation of the existing system on the basis of understanding the current architecture. How to switch economy from the original technology architecture to the SOA architecture has become a problem for many enterprises.

XFire Overview

XFire is an open source framework provided by the Codehaus organization that builds a bridge between POJO and SOA, with the main feature supporting the release of POJO to Web services in a very simple way, which not only gives full play to POJO, but simplifies Java application transformation The steps and procedures for WEB services also directly reduce the difficulty of SOA implementation, providing a simple and workable way for an enterprise to move to an SOA architecture.

The latest version of XFire is 1.2.2, and the features currently supported include:

Supports binding Web services to POJO, XMLBeans, JAXB1.1, JAXB2.0, and Castor;

Support access to WEB services based on HTTP, JMS, XMPP, and many other protocols;

Support a wide range of Web services industry-critical standards such as SOAP, WSDL, Web Service Addressing (ws-addressing), Web Service Security (ws-security), etc.

Support JSR181, you can configure WEB services through JDK5;

High-performance SOAP implementations;

Server side, client code-assisted generation;

Support for projects like Spring, Pico, Plexus, and so on.

XFire installation Package

The latest version of the XFire framework is 1.2.6, which can access the xfire.codehaus.org download XFire Framework installation package, please select "All binary publishing packs (Binary distribution in zip package)" when downloading. Rather than just "XFire jar files (jar all XFire modules)".