Using C API for XML

XML uses the C API parser for XML developer's kit and XML Database in oracle. It can be considered as a C based Data object model for XML. Whether the data is out side or inside the databases, irrespective of the situation it can be used in XML.

There are some performance improving extensions and parameters which is an integral part of this API which can be used in XML like the ML developers kit which can be used for storage of XML in a traditional pattern and the Oracle ML database which can store the XML as XML type in the table in one of the columns.

In the Oracle XML database the C API is started in XML only. The World Wide Web Consortium highly recommends the DOM, which has a very broad meaning for the word document itself. The programming interface in the C API environment is a combined effort and it also includes all the required functions which are needed by XML developer's kit and Oracle XML Data Base using applications.

XSLT is provided for these databases and the XML Schema is also implemented. Even though the World Wide Web consortiums highly recommended DOM 2.0 was closely adhered to and followed, still further naming changes were required and had to be implemented in the DOM 2.0 like the recommendation for C namespace for example and another example is that the method called getName() had to be renamed to getAttrName().

The C API for XML is super fast and overtakes all the existing API's. Especially, the oraxml and the oraxsd.h interface which is top-level in Data Object Model and SAX, and also the XSLT along with the XML schema interfaces which has high chances of facing criticism in the future of the XML and C scenario.

Support for storage is provided by the XML data base and it also allows the XML instances to be manipulated by using the data type which is XML type. The XML instances that can be accessed and even manipulated by using tools like Oracle Call interface or OCI in a unanimous combination with the C data object model API for extensive markup language.

Every application program for its flow of information would involve all the data object model functions for C. The Oracle XML data base which stores the XML data can be accessed by the client side by using the structure in C data object model called the xmldocnode. The xmldocnode structure is mainly used in the database for functions like binding and defining, operating the Oracle call interface values in XML.

C DOM API functions require all the parameters in the XML context. The information that is encapsulated in a very opaque manner while the process of data encoding is taking place, and processes like the error message coding is going on.

Oracle XML Developers Kit applications and Oracle XML Data Base are quite different from each other because the content in their context itself is very different. For Oracle XML Data Base itself there are two Oracle Call Interface functions which will initiate the function called OCIXmlDbInitXmlCtx() and will terminate the function called OCIXmlDbFreeXmlCtx() in an XML context.

Integrating Oracle and C

In the C environment the dynamic C and C++ libraries which are binary or static or dynamic can be integrated with the language in use and its environment without having the need to recompile the while thing all over again. Any C or C++ application can be deployed effectively even in cross platforms using the CH XML package which is an integral part of the Oracle XML Library. They can be deployed on the internet also.

Integration with DOM API

The data object model of API in XML will create a tree structure which will store the XML documents within the memory itself. There are no call back functions that are available for the data object model based CML c or C++ applications. In any case it is very simple to create a CH binding for the Oracle data object model API for the XML developer kit.

The oracle XML developers Kit gels well with the CH. There are three layers in the architecture mainly, the user applications is on the first layer, which consists of the applications that are using the libraries in C and C++. The second layer consists of the CH wrapper which acts as the middleware for the functions which interpret using text based coding and the binary functions. The CH wrapper also known as the CH binder has been mainly developed for usage in the XML developer's kit. The source code is freely available for the CH binder on the internet.

For the CH binding to be deployed on different platforms the open source can be used and also with the different versions of the XML developers kit. In some cases as the main functions version gets upgraded the accessories get left behind and sometimes turns incompatible with the main function itself. SO again a different process is invoked to upgrade the accessory also. The last layer consists of the authentic and original C and C ++ binary data which is provided by the XML developers kit.

Online Resource
Codalogic
Ch

Using C API for XML

Integrating Oracle and C

Integration with DOM API

Tags