Meta tags:

Headings (most frequently used words):

xom, about, java, api, downloads, for, contributors, third, party, articles, projects, using,

Text of the page (most frequently used words):
xom (48), the (33), and (28), xml (25), you (25), that (14), with (13), api (12), for (11), source (11), code (10), tests (8), sample (8), programs (8), jars (8), can (8), third (7), party (7), unit (7), documents (7), documentation (6), are (6), includes (6), parser (6), only (6), java (5), design (5), complete (5), should (5), have (5), not (5), all (5), tree (5), very (5), your (5), dependency (5), using (4), principles (4), from (4), future (4), about (4), don (4), get (4), version (4), into (4), document (4), sax (3), data (3), what (3), wrong (3), tar (3), zip (3), tutorial (3), mailing (3), faq (3), more (3), parts (3), read (3), based (3), need (3), non (3), subscriber (3), this (3), xerces (3), them (3), add (3), built (3), memory (3), piece (3), well (3), testing (2), jdom (2), dom (2), apis (2), test (2), suite (2), building (2), distribution (2), format (2), jar (2), file (2), repository (2), javadoc (2), copyright (2), directions (2), xpath (2), mapping (2), 2026 (2), elliotte (2), rusty (2), harold (2), cafe (2), lgpl (2), interested (2), like (2), suggest (2), way (2), questions (2), possible (2), interest (2), list (2), backwards (2), compatible (2), versions (2), any (2), xslt (2), support (2), depends (2), xinclude (2), underlying (2), while (2), work (2), later (2), fairly (2), parsers (2), many (2), than (2), when (2), gradle (2), groupid (2), artifactid (2), maven (2), canonical (2), little (2), allows (2), nodes (2), white (2), space (2), application (2), process (2), has (2), unique (2), correctness (2), namespace (2), formed (2), easy (2), prebuilt (2), fisheye, smartfrog, conformance, wurfl, carrierwave, memoranda, json, lib, excemel, openinfocard, sleep, concordion, projects, made, simpler, getting, started, organic, schemas, outlier, human, side, designing, dictatorship, examples, air, bags, other, lessons, learned, review, good, bad, articles, contributor, agreement, contributors, minimal, downloads, lists, license, infoset, installation, instructions, release, notes, 2002, last, modified, may, elharo, ibiblio, org, lait, con, leche, cafes, commercial, licenses, available, companies, wish, bundle, their, products, without, subscribing, contact, know, starting, also, large, collection, small, demonstrate, various, library, curious, why, would, which, question, answered, ask, subscribed, post, but, moderated, due, increasing, amounts, spam, missed, answer, subscribe, try, again, current, back, recompile, upgrade, believed, quite, stable, robust, releases, foreseeable, similarly, trax, processor, canonicalization, however, native, unto, itself, feed, structure, theoretically, sax2, compliant, one, confident, does, repackaged, most, contemporary, jdks, piccolo, crimson, gnu, jaxp, 0b1, oracle, prior, bugs, prevent, doing, needs, note, vendors, gives, thorough, workout, delves, obscure, spec, could, lot, worse, making, sure, pass, dependencies, compile, group, its, artifact, element, pom, number, technologies, including, namespaces, base, exclusive, converted, efficient, entire, uses, importantly, filter, they, build, aren, instance, skip, text, represent, boundary, such, significant, even, throw, away, each, done, been, used, gigabytes, size, dual, streaming, individual, processed, still, being, enables, operate, almost, fast, supply, wait, completely, parsed, before, start, working, makes, compromises, accepts, create, fact, stricter, actually, guarantees, round, trippable, defined, infosets, manages, focus, value, trust, right, designed, learn, use, works, straightforwardly, shallow, learning, curve, assuming, already, familiar, able, running, quickly, core, packages, how, fix, new, object, model, open, processing, strives, simplicity, performance, order,

Text of the page (random words):
xom xom xom is a new xml object model it is an open source lgpl tree based api for processing xml with java that strives for correctness simplicity and performance in that order tutorial javadoc what s wrong with xml apis and how to fix them faq jar file core packages only complete zip includes source code prebuilt jars api documentation unit tests sample programs third party jars complete tar gz includes source code prebuilt jars api documentation unit tests sample programs third party jars source code zip includes source code unit tests sample programs third party jars source code tar gz includes source code api documentation unit tests sample programs third party jars xom interest mailing list source repository xom is designed to be easy to learn and easy to use it works very straightforwardly 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 this 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 1 0 xslt 1 0 xinclude xml id xml base canonical xml and exclusive canonical xml xom documents can be converted to and from sax and dom xom s maven group id is xom and its artifact id is xom to add a dependency on xom using maven add this dependency element to your pom xml dependency groupid xom groupid artifactid xom artifactid version 1 4 4 version dependency to add a dependency using gradle gradle dependencies compile xom xom 1 4 4 xom is not complete unto itself it depends on an underlying sax parser to read documents and feed the data into a tree structure while theoretically any sax2 compliant parser should work xerces 2 6 1 and later is the only one that i am fairly confident does work this or a later version of xerces is repackaged into most contemporary jdks piccolo 1 0 3 crimson gnu jaxp 1 0b1 the oracle xml parser for java 9 2 0 2 0d and 9 2 0 5 0 and xerces versions prior to 2 6 1 all have bugs that prevent them from doing what xom needs them to do note to xml parser vendors xom s test suite gives parsers a very thorough workout and delves into many of the more obscure parts of the xml spec that many parsers get wrong you could do a lot worse for testing than making sure all the xom unit tests pass when using your parser similarly xslt support depends on a trax processor xinclude and xml canonicalization however are native the current version of xom is 1 4 4 and is backwards compatible with all versions from 1 4 0 all the way back to 1 0 you should not need to recompile any code to upgrade to 1 4 4 xom is believed to be quite stable and robust future releases should be backwards compatible with the 1 0 api for the foreseeable future if you d like to know more about xom i suggest starting with the tutorial xom also includes a large collection of small sample programs that demonstrate various parts of the library if you re curious about why xom is the way it is or if you would like to suggest future directions for xom you should read the design principles on which xom is based if you have a question about xom that is not answered in the api documentation or the faq you can ask it on the xom interest mailing list you do not need to be subscribed to post but non subscriber questions are moderated due to increasing amounts of non subscriber spam it is possible non subscriber questions are missed if you don t get an answer subscribe and try again commercial licenses are available for companies that wish to bundle xom with their products without subscribing to the lgpl contact elliotte rusty harold if you re interested the cafes cafe con leche cafe au lait copyright 2002 2026 elliotte rusty harold elharo ibiblio org last modified may 13 2026 about xom design principles release notes faq installation instructions infoset mapping xpath mapping future directions license and copyright mailing lists java api tutorial javadoc sample code downloads source repository minimal jar file complete distribution zip format source code api documentation unit tests sample programs third party jars complete distribution tar gz format source code api documentation unit tests sample programs third party jars for contributors contributor agreement building xom test suite third party articles what s wrong with xml apis the good the bad and the dom a design review of jdom lessons learned from jdom design principles and xom air bags and other design principles designing by dictatorship examples and tests the human side of xml organic schemas and outlier data getting started with xom the xom java xml api java xom xml made simpler projects using xom concordion sleep openinfocard excemel json lib memoranda carrierwave wurfl sax conformance testing smartfrog fisheye