Hi!
Taking a look at a problem I'm having at my day job right now, I noticed
the BeanModel classes (including PropertyModel, PropertyConduit,
BeanModelSource, etc) could be hugely useful for projects and code that
need to deal with class properties: discovery, reading and writing
properties. Tapestry does that and in a very fast manner, as it doesn't
use reflection at all for reading and writing properties. Our scenario
here is a homegrown XML mapper that cannot be replaced due to backward
compatibility and we'd also need some lazy-loading of mapped properties,
as most of the time most properties aren't needed
BeanModel et al is inside tapestry-core, so anything using it would need
to depend on an (awesome) Tapestry framework. I believe with a little bit
of work, including a sprinkle of Gradle magic, we could generate a
BeanModel JAR separate from tapestry-core.
What do you guys think?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
