On Fri, 21 Mar 2014 06:22:32 -0300, Guillaume Bodet <gbo...@gmail.com>
wrote:
Hi all,
Hi!
Any idea where I should start?
I think you're looking at the wrong part of Tapestry for the solution. I
think the best solution would be to implement a new binding that would be
heavily based on the prop one Tapestry already provides. Or you can
decorate or advise the services used in the prop binding so you can inject
your fallback logic.
--
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
