Vs Simple

[Benjamin Darfler]

I was wondering if anyone can talk briefly about how xmappr stacks up
with simple?

http://simple.sourceforge.net/home.php

[Peter Knego]

Hi Benjamin,

From a brief look at Simple's dosumentation it seems to be oriented towards object serialization and is as such more comparable to Xstream. Xmappr is designed to support mapping "external" XML, e.g. XML that comes from external sources, where one does not control the schema.

However, given proper configuration, both Simple and Xmappr can perform similar tasks.

Quick comparison checklist :
- configuration via annotations: both
- configuration via xml: Xmappr
- basic Attributes, Elements and Text mappings: both
- nested mappings: both
- mixing Text and Elements: Xmappr
- partial mapping: Xmappr
- constructor injection: Simple (planned for Xmappr)
- default values: Xmappr (is seems that Simple can achieve this via it's Filters)
- namespaces: both
- preserving order of Elements: both

This list was devised from quickly looking at Simple's documentation - please correct me if I got anything wrong. Also the list does not try to cover all features.

Peter

[Benjamin Darfler]

Thanks, thats really helpful. I'll keep all three options in mind for
the future.

Ben

On Jan 1, 5:56 am, Peter Knego <pe...@knego.net> wrote:
> Hi Benjamin,
>
> From a brief look at Simple's dosumentation it seems to be oriented towards
> object serialization and is as such more comparable to Xstream. Xmappr is
> designed to support mapping "external" XML, e.g. XML that comes from
> external sources, where one does not control the schema.
>
> However, given proper configuration, both Simple and Xmappr can perform
> similar tasks.
>
> Quick comparison checklist :
> - configuration via annotations: both
> - configuration via xml: Xmappr
> - basic Attributes, Elements and Text mappings: both
> - nested mappings: both
> - mixing Text and Elements: Xmappr
> - partial mapping: Xmappr
> - constructor injection: Simple (planned for Xmappr)
> - default values: Xmappr (is seems that Simple can achieve this via it's
> Filters)
> - namespaces: both
> - preserving order of Elements: both
>
> This list was devised from quickly looking at Simple's documentation -
> please correct me if I got anything wrong. Also the list does not try to
> cover all features.
>

[Pangea]

whats the advantage of partial mapping (apart from the fact that i
dont need those extra elements/attributes)??? we are parsing the whole
doc anyway!. are there any performance improvements of using partial
mapping?

[Peter Knego]

The main advantage is to avoid the extra mapping configuration (which can be substantial in some cases).
As I noted in another reply - there is no way around parsing the whole XML document. XML is a stream of data and is not a random access medium.
Partial mapping still processes the XML and stores it internally. So I expect no substantial speed improvements versus full mapping.

Peter