GitXplorerGitXplorer
n

devourer

public
0 stars
0 forks
1 issues

Commits

List of commits on branch master.
Verified
6ed180aee6f62cc1ecacc2c7c0ef4201ad9cb788

Update README.md

nnetvl committed 4 years ago
Unverified
33066eec17d322de8e1457b5ee64e7655159241a

Many changes, preparing for the next release

nnetvl committed 12 years ago
Unverified
a1ab66ae9d0a2e3693ef96d7fa102b98948dd0e0

Added @Attribute annotation support to annotated configuration

nnetvl committed 12 years ago
Unverified
64d0434ed59be6a10e1b1eb7cbbd42c15e0b2d96

First integration tests for annotated configuration done; also added Peek/PopList[From] annotations support

nnetvl committed 12 years ago
Unverified
ce4095a70a42779c1122be61b05dbb527bacb426

First integration test works, plus added convenience list accessors to stacks

nnetvl committed 12 years ago
Unverified
420ad06ab674db00ee42e4627fdd0e76d1a7ed25

Slightly restructured integration tests

nnetvl committed 12 years ago

README

The README file for this repository.

Devourer - simple XML processing library

Unmaintained.

Devourer is simple streaming XML processing library written in Java taking advantage of modern XML parsing library and providing easy-to-use API, which is compatible with latest Java releases, i.e. Java 8 and its Project Lambda.

Devourer is heavily inspired by Apache Digester. Devourer essentially performs the same job as Digester, but it avoids heavy use of reflection (thus making your XML processing way faster) and it also uses StAX processing library instead of SAX, which leads to much simpler and easier to support architecture, as well as nearly effortless thread safety. Devourer also has minimal amount of runtime dependencies (only Google Guava library).

Installation

Devourer is present in Maven Central. You can add it to your Maven dependency list:

    <dependency>
        <groupId>org.bitbucket.googolplex.devourer</groupId>
        <artifactId>devourer</artifactId>
        <version>0.1</version>
    </dependency>

Usage

See here for the user manual.

Notes

There are several points I think I should note about the library.

  • Namespace support is far from adequate. Currently all namespace filtering must be done inside actions; also namespaces are mostly handled via prefixes, not real namespace identifiers. This should change in the nearest future.
  • The library is not covered by automatic tests. This is also likely to change soon.
  • Support for wildcards in element paths is completely absent. This would be very nice feature to have, and I may add it one day.