hi, can you post some code.
i guess you are in tapestry production mode g, kris Yury Luneff <bitter...@ya.ru> 19.02.2010 04:42 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An "Tapestry users" <users@tapestry.apache.org> Kopie Thema exceptions sometimes are omitted completely Hello! I'm fighting with my app for features now. There is a problem about valueencoders and such and i guess this problem should report as any kind of exception - either the beautiful one done by tapestry or at least stacktrace in log window. But tapestry chooses neither. Just empty page and that's all. Sometime ago this also happened a lot - one mistake in property binding and you get the right exception sometimes, but sometimes you get completely nothing. "Debug" in log4j doesn't quite help here. Did anyone meet that behavior? It is very unpleasant to debug something with empty pages and no exceptions (log4j, btw, is set for error level as default which should do exceptions). --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
