Sorry Thaigo, but I am not sure what you had in mind. If you think about
That's something to avoid as much as possible. Well first I am not sure why is this the case. If tapestry supports passing configurations in this way then it should support passing functions when those configurations are expecting them. However I would be open to avoid doing this but I dont see a way to do it, other then overwriting javascript files and putting my code directly there. I was able to identify the scenario that leads to this problem. The ajaxUpload component needs to be surrounded by the zone, if that is not the case then a function can be passed without any issues. Sadly in my code the zone is necessary. I will try to reach to the tapestry5-jquery developer to see if he thinks this is a bug and can it be fixed. Thanks for the help and please if you have any idea how to avoid passing the function (that doesn't involve overwriting existing files) I will be happy to try it out. Cheers On Tue, Feb 25, 2014 at 3:10 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 24 Feb 2014 19:53:59 -0300, Boris Horvat <horvat.z.bo...@gmail.com> > wrote: > > Anyone has any idea about this? :) >> > > I already gave you my suggestion. > > > -- > 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 > > -- Sincerely *Boris Horvat*
