On Mon, 19 Jan 2015 17:23:36 -0200, Howard Lewis Ship <hls...@gmail.com>
wrote:
- Split more code out into smaller modules, to encourage reuse (even
outside of a Tapestry web application)
Specifically, two new subprojects/JARs were created: BeanModel (everything
you need to use BeanModel without any dependence on tapestry-core or
tapestry-ioc) and Common (stuff from tapestry-ioc and tapestry-core that
is used in the BeanModel subproject, but represents concepts that aren't
specific to BeanModel, such as Registry, TypeCoercer, etc). This is all
100% backward-compatible: all classes that were moved to either BeanModel
or Commons have the same names and belong to the same packages as before.
This was done with the intention of using the Tapestry's BeanModel classes
as a very fast Java property reflection library without the need to use
Tapestry-core (the Web framework) nor Tapestry-IoC.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
