You can also use log4j's e-mailing capabilities and set an log.error("") on your Tapestry. That way you don't have to reimplement the error reporting (log4j even includes some previous debug / info logging messages as a nice feature).

--
Ing. Leonardo Quijano Vincenzi
Director Técnico
DTQ Software


Andrey Tkach escribió:

Yep, it's interesting. Could you please post your code here (with an ant
build file)

Andrey

We are using that with Tapestry 3. I can post my code if you are
interested.
I have configured our ant build with 2 targets dev and production, on
dev the exceptions are showed normally but on prod, another page is
displayed and an email is sent.

Henri.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to