xml-test checks that an XML document is included in another document. It is handy when testing an application's output against a document where element order is different (GData and Atom are examples of specifications where element order is unimportant). It has a relaxed notion of containment: element order is ignored, whitespace is trimmed, comments are ignored, specific elements can be ignored by passing XPath-like paths on the command line, and text nodes (element and attribute content) can be ignored by passing '-notext' on the command line.
xml-ui-viewer is a simple tool for viewing user interfaces defined in an XML file and rendered using SwixML. It may be useful during the design stage of software development as it makes it possible to quickly write user interface forms, render them, and show the result to a customer. In the actual implementation stage, the "prototypes" can be used in a real application.
XmlBlaster is XML based MOM (Message oriented Middleware) with a lot of features. It is a publish/subscribe and point-to-point MOM server which exchanges XML-encoded messages. Communication with the server is based on CORBA (using JacORB), RMI, XML-RPC, native socket, or a persistent HTTP plugin. Subscribers can use XPath expressions to filter the messages they wish to receive and add their own MIME-based filter plugins. C/C++, Java, Perl, Python, VisualBasic.net, C#, and PHP client demos are included in the xmlBlaster test suite, and Tcl and Python demo clients are scheduled. XmlBlaster also provides a browser callback framework, allowing browsers (Netscape, Mozilla, MSIE) to receive instant callbacks over a persistent http connection. A security plugin framework allows authentication/authorization in many ways. Currently there are LDAP- and passwd-based plugins available.
XML::RDB is a Perl extension to convert XML files into RDB schemas and populate/unpopulate them. It works with XML schemas too. It analyzes relationships within either an XML file or an XML schema to create RDB tables to hold that document (or any XML document that conforms to the XML schema). It takes an XML file or URL as input for the XML::DOM::Parser, and extracts information to build and write DDL. An attempt is made to recognize relations within the XML structure then translate it to the DDL. That generated DDL is then loaded, parsing the DOM tree a second time to extract and load the data. At the bottom of the DDL are select statements to help get a view of those relations found, and XML data. xml_rdb also dumps the data back to XML format.
xmlizer configurator/server is a client/server approach for custom database to XML mapping. The configurator is used to set up projects and the server delivers the processed requests on demand (like a Web server) according to the mapping rules made with the configurator, which includes a drag and drop GUI. One module is for dumping databases (or parts of it) in a fixed format and the other module can build XML instances satisfying a specified XML Schema (or DTD).
The goal of xmlportlet is to provide a base portlet to serve as a simple mechanism for transforming XML data into the view for your portlet application. This base portlet will be JSR-168 compliant, and will relieve you from developing the basic boilerplate logic needed to transform XML using XSLT into HTML.