Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
XOM is designed to be easy to learn and easy to use. It works very straight-forwardly, and has a very shallow learning curve. Assuming you're already familiar with XML, you should be able to get up and running with XOM very quickly. XOM is the only XML API that makes no compromises on correctness. XOM only accepts namespace well-formed XML documents, and only allows you to create namespace well-formed XML documents. (In fact, it's a little stricter than that: it actually guarantees that all documents are round-trippable and have well-defined XML infosets.) XOM manages your XML so you don't have to. With XOM, you can focus on the unique value of your application, and trust XOM to get the XML right. XOM is fairly unique in that it is a dual streaming/tree-based API. Individual nodes in the tree can be processed while the document is still being built. The enables XOM programs to operate almost as fast as the underlying parser can supply data. You don't need to wait for the document to be completely parsed before you can start working with it. XOM is very memory efficient. If you read an entire document into memory, XOM uses as little memory as possible. More importantly, XOM allows you to filter documents as they're built so you don't have to build the parts of the tree you aren't interested in. For instance, you can skip building text nodes that only represent boundary white space, if such white space is not significant in your application. You can even process a document piece by piece and throw away each piece when you're done with it. XOM has been used to process documents that are gigabytes in size. XOM includes built-in support for a number of XML technologies including Namespaces in XML, XPath, XSLT, XInclude, xml:id, and Canonical XML. XOM documents can be converted to and from SAX and DOM.
Package | Summary | Distribution | Download |
xom-1.3.9-2.2.noarch.html | XML Object Model | OpenSuSE Tumbleweed for noarch | xom-1.3.9-2.2.noarch.rpm |
xom-1.3.9-2.2.noarch.html | XML Object Model | OpenSuSE Ports Tumbleweed for noarch | xom-1.3.9-2.2.noarch.rpm |
XML Object Model | xom-1.3.9-2.2.noarch.rpm | ||
xom-1.3.9-slfo.1.2.1.noarch.html | XML Object Model | OpenSuSE Leap 16.0 for noarch | xom-1.3.9-slfo.1.2.1.noarch.rpm |
xom-1.2b1-150200.12.4.4.noarch.html | XOM is a new XML object model | OpenSuSE Leap 15.5 for noarch | xom-1.2b1-150200.12.4.4.noarch.rpm |
xom-1.2b1-150200.12.4.4.noarch.html | XOM is a new XML object model | OpenSuSE Leap 15.6 for noarch | xom-1.2b1-150200.12.4.4.noarch.rpm |
Generated by rpm2html 1.6