On Thu, Apr 9, 2009 at 12:11 AM, Raoul Duke <[email protected]> wrote:
> i don't mean to be late-to-the-game or overly critical, i mean this as > an honest question: are there possible alternatives to using XML in > Qi4J? what are your feelings / experiences about the best approaches > to configuration? No XML used will be visible nor editable by human beings. For configuration, there is a two step process; 1. The initial configuration is read from properties files. 2. It is then stored as an Entity, to be edited with domain tools. Both Rickard and I are 'allergic' to the notion of "Joe Doe" editing text(!) files (XML or otherwise) that affects the execution, and we insist that good applications provide deployment, configuration, management tooling as part of the delivery. One question that kind of can be asked on this topic is; Is XStream the fastest serializer available?? Our criteria are pretty well known; 1. The object graph is relatively small, so startup time is crucial. 2. The serialized format must be robust, and have good tooling available. 3. Must allow metadata to be attached. Anyone got better ideas than XStream? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
