1 個解答
- ApricotLv 61 十年前最愛解答
In much the same way that WSDL (an XML document format) defines SOAP transactions, General Interface employs a tree-like definition language of its own referred to as the Common Exchange Format (CXF). Using a common format for defining transactions allows General Interface to communicate with a myriad of systems without being tied to a particular interface definition. CXF documents are created at design time by the XML Mapping Utility, using any number of formats as a starting point for creating the definition. Supported formats include WSDL, Schema, XML, and XHTML to name a few.
Once parsed by the XML Mapping Utility, XML documents are persisted in CXF format, meaning they can be mapped to application objects such as CDF Documents, textboxes, and nodes in the local XML Cache. Regardless of whether WSDL, Schema, or XML is used, all input formats result in the same transactional format. In practice, this means that a the interactions with a SOAP service can be defined by using either the WSDL or a sample SOAP message (e.g., Envelope) as a starting point. Ultimately, the source type (WSDL, Schema, or XML) used to create a CXF rules document is irrelevant once the CXF document has been created, as all formats are persisted using CXF.
Another way to think about CXF is to consider it an interpretive language that is able to interface between the XML document formats used by a given Web Service and the native CDF and JavaScript formats used by General Interface. Just as it is important to be versed in CDF in order to know how data is used within General Interface, an understanding of CXF provides insight into how data is shared between General Interface and data services. While CDF provides the format for data while it is within the control of General Interface, CXF provides the bridge to convert this information to the format required by the given web service.
