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 too due to TypeCoercer, ObjectLocator,
DataTypeAnalyzer, AnnotationProvider. I think the new JAR could get
DataTypeAnalyzer and AnnotationProvider, ObjectLocator is only used for
object instantiation, so its direct use is easily replaceable. TypeCoercer
would be difficult to replace, but I haven't dived in this specific part
yet.
Having a Tapestry-IoC dependency wouldn't be a problem, I 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
