Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

xom-1.2b1-19.1.1 RPM for noarch

From OpenSuSE 12.2 for noarch

Name: xom Distribution: openSUSE 12.2
Version: 1.2b1 Vendor: openSUSE
Release: 19.1.1 Build date: Sun Jun 24 07:22:27 2012
Group: Development/Languages/Java Build host: build09
Size: 1432064 Source RPM: jdom-1.1-19.1.1.src.rpm
Packager: http://bugs.opensuse.org
Url: http://www.jdom.org
Summary: XOM is a new XML object model
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.

Provides

Requires

License

LGPL-2.1+

Changelog

* Fri Jun 15 2012 mvyskocil@suse.cz
  - ignore jdk7 as well
* Mon Jun 04 2012 coolo@suse.com
  - remove stray character from xom summary to fix UTF-8 parsing
* Thu Mar 17 2011 mvyskocil@suse.cz
  - move to gcj back - the java.lang.StackOverflow is nothing nice
* Fri Mar 11 2011 mvyskocil@suse.cz
  - build using openjdk, split BR one per-line
* Fri Mar 11 2011 mvyskocil@suse.cz
  - build using openjdk, write one BuildRequire per line,
    no authors in description
* Wed May 20 2009 mvyskocil@suse.cz
  - 'fixed bnc#501764: removed clover.license from source tarball'
* Mon May 18 2009 mvyskocil@suse.cz
  - Removed documentation of ConcurrentReaderHashMap (bnc#504663)
    * dom4j-1.6.1/docs/clover/org/dom4j/tree/ConcurrentReaderHashMap.html
    * dom4j-1.6.1/docs/xref/org/dom4j/tree/ConcurrentReaderHashMap.html
* Thu May 14 2009 mvyskocil@suse.cz
  - fixed version tag for jaxen and xom
* Tue Jan 20 2009 mvyskocil@suse.cz
  - update jdom to 1.1 fixed bnc#467366
  - updated jaxen to 1.1.1 (do not use an included jaxen)
  - cleaned build requires
  - Obsoleted java150 patch
* Fri Nov 21 2008 ro@suse.de
  - update check-build.sh

Files

/usr/share/java/xom-1.2b1.jar
/usr/share/java/xom.jar


Generated by rpm2html 1.8.1

Fabrice Bellet, Fri Oct 10 12:29:33 2014