The Tynamo list has never worked for me. It seems that it works for some users and not others. I get a bounced E-mail when I send it to the tynamo list.
On Nov 24, 2011, at 1:36 PM, Nicolas Barrera wrote: > Hi Ale, > > thanks for the help, so you say that tynamo's mailing list should be > working alright but just for moment to moment is down? then i 'll be > retrying to post there. > > About what you answered me... > > i 've finally avoided the problem overriding the isAllowRemove method > calling one of the bean's specific method which tells me if it has children > relationship, then instead of the delete link I print a "you can't delete" > message. > > About what you suggested... I can file a Jira issue no problem (and post > the patch if I can), but let me be sure that I understand your proposal..., > > > You 'd like to modify Tynamo's Show page's method onActionFromDelete > catching up a JDBCBatchException or something like that? > > I was thinking about that and I would catch an HibernateException and > return a link to the same page..., what I 'm not sure is about the way to > report the error to the end user... > is there any component which shows an overlay/modal with the error message? > Anyway the HibernateException could be any error not only this kind of > database error. > > well about the second error on my second mail, it was something else I was > doing wrong that I could solve, and the difference between Locality and > Sucursal was just me trying to translate my class names :S > > > if the tynamo list is up, then i will continue this thread there, > > thanks again, and I 'll wait for your comments on my ideas about the patch. > > cheers, > > Nicolás.- > > > On Thu, Nov 24, 2011 at 1:54 PM, Alejandro Scandroli < > alejandroscandr...@gmail.com> wrote: > >> 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 >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
