hi,
starting a new project, i'm thinking about the basic architecture and
which components to use. since it's a small project, using the whole
ofbiz-framework seems to be overdone. but i will need a persistence
layer for the new application. and since i'm curious on using
ofbiz-components in a real project, i think about using the entity engine.
before making a decision, i want to compare the entity engine to other
possible sollutions (e.g. jdo, hilbernate, castor). can someone give me
some hints about such comparisons. especially i'm interested in the topics:
- performance (of course)
- robustness (error recognition, transactions),
- extensibility (of the data-model while there is allready data in the
database)
- flexibilty (using something like sql-joins to combine entites)
- usage (ease of usage, modelling/maintenance-tools)
as far as i read the docs, i can see a lot of things i really like. what
i dislike is the fact, that accessing the value-object attributes is
through a string-name-parameter. in case of typos (or name-changes),
which could easily be found at compile-time if i had a pojo-interface,
applications that use the entity engine will compile successful but run
into runtime errors. did i miss something important here? what is the
best practice to avoid this kind of problems?
thanks in advance,
andi
_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users
Locked
