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
Sounds useful. I'm assuming plastic would need to be on the classpath but
tapestry-ioc would not?
On Wed, 08 Oct 2014 13:40:48 -0300, Lance Java lance.j...@googlemail.com
wrote:
Sounds useful. I'm assuming plastic would need to be on the classpath but
tapestry-ioc would not?
I haven't investigated much yet, but it would need a dependency on Plastic
for sure and probably Tapestry-IoC
See https://builds.apache.org/job/tapestry-trunk-freestyle/1338/changes
Changes:
[kaosko] FIXED - TAP5-2396: DefaultExceptionHandler doesn't currently recognize
--
[...truncated 16815 lines...]
at
