I have seen this "Form components may not be placed inside other Form components." error way too many times. The problem is that your ExceptionReport page has a form that is trying to add a new FormSupport to the environment but there is one already there. The FormSupport that is already on the environment is from the form that failed and threw exception.
If you can't avoid having a form in your ExceptionReport page you can try adding a fail safe to revert back to Tapestry's default ExceptionReport when there is an exception in the exception page. I've just filed JIRA issue (http://jira.codehaus.org/browse/TYNAMO-107) to fix this in Tynamo's tapestry-exceptionpage. The patch is just around the corner. Cheers. Alejandro. On Mon, Dec 5, 2011 at 10:23 AM, Stephan Windmüller <stephan.windmuel...@tu-dortmund.de> wrote: > On 30.11.2011 15:55, I wrote: > >> However, now the ExceptionReport page itself throws an exception when >> the orginal exception occurs on a page which already has a form: > > Does anybody have an idea why this is happening or how I can fix it? > > Regards > Stephan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
