GitXplorerGitXplorer
n

devourer

public
0 stars
0 forks
1 issues

Commits

List of commits on branch master.
Unverified
94c6468d32969e25afdd2132daced06fa40afc30

Refactored annotated configuration classes and moved integration tests

nnetvl committed 12 years ago
Unverified
ba523c2d006b9e663ecf95d594288957bb2af64f

Finished tests for modular configuration

nnetvl committed 12 years ago
Unverified
c1ae33ba6b29be89bd9756a144ea3c332b1245ef

Started writing tests for modular configuration

nnetvl committed 12 years ago
Unverified
8942ce9b8c9abcc081820969bbabaeda1617e939

Fixed weird PathMapping which has not been committed

nnetvl committed 12 years ago
Unverified
fc2a70d36de3c7ed56f7ee868c7b310502c9d4e3

Updated configuration code to use new patterns and paths and namespace contexts

nnetvl committed 12 years ago
Unverified
80489b7d3978512474d28a4b6ffd1e4ba7e83612

Patterns almost finished, wrote global wildcards matching

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.