Hi Nicolás > > - Am I obliged to make a custom page in order to catch up that exception > and show the user a friendly message? (something like "hey!, you can't > delete this locality as it's referenced by other persons") >
No really, you can catch the exception in your own Show.java page overriding (onActionFromDelete). You can also try some other (weird bidirectional) mapping alternatives, but I think the cleanest option is the custom page. I think this could be a nice thing to add by default, since it could be a very common issue. Do you mind filing a JIRA issue for it? (a patch would be wonderful btw) > - I 've read about the tynamo-exceptionpage module which I think it will > catch up the error, but will show a generic error message per exception I > register am I right? > That's exactly right! > (….) > the result is that after I create a new Locality, it forwards to the show > locality page but before rendering this error shows up: > > org.apache.tapestry5.internal.services.RenderQueueException I don't know what could be wrong here. I need for info. The only thing weird I see is that if the page name is LocalityShow, the getType() method should return Class<Locality> instead of Class<Sucursal> BTW, you are not the first reporting problems with tynamo's user list, but still can figure out why sometimes doesn't work. I will try (again) to send a test email later. Thanks and welcome. Saludos. Alejandro. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
