Hi,
good point. one dependency to a XML framework is enough. we can keep
JAXB (which is part of the JDK anyway) or use the Apache Digester, which
I haven't used yet.
XStream is only required for the non-jsr303 parts. We can remove some
code in this area (e.g. dependencies to freemarker, xstream) or do we
want to keep these non-jsr303 functionality?
Roman
--- Simone Tripodi<[email protected]> schrieb am Mo, 29.3.2010:
Von: Simone Tripodi<[email protected]>
Betreff: [DISCUSS] conversion utilities
An: [email protected]
Datum: Montag, 29. März, 2010 14:27 Uhr
Hi all guys,
during the package move, I noticed few minor points I'd
like to
discuss with you all:
1) a conversion utility has been (re)implemented, so I
wonder why we
don't reuse the Apache Commons BeanUtils (already in the
dependencies)
built in ConverterUtils instead of reimplementing stuff.
What do you think about it?
2) about the XML libraries: I noticed we've JAXB and
XStream
dependencies, since our scope AFAIK is just parsing XML,
wouldn't more
convenient, with the objective of reducing the number of
dependencies,
just use the Apache Commons Digester instead? The only big
dependency
it has is the Apache Commons BeanUtils (already in the
dependencies)....
Sorry for the silly questions and thanks in advance for
your reply :)
All the best!
Simo
http://people.apache.org/~simonetripodi/
__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen
Massenmails.
http://mail.yahoo.com
