got it,
same as me.
Nicolás.-
**
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**
The original message was received at Wed, 22 Jun 2011 08:26:07 -0400
from user-0cdfs5f.cable.mindspri
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
> work
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
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
over
Hi, I went for customizing the Location page,
generated a pages/show/LocalityShow.java and .tml
the tml I copied it from the Show.tml file
and the .java I overrided the following methods:
public Class getType() {
> public Link onActionFromDelete() {
> public boolean isAllowRemove()
Hi all, (sorry I 'm asking about tynamo on Tapestry's user list but I tried
to use us...@tynamo.codehaus.org but mailer said it wasn't working)
Here goes a newbie question runner up...:
I got a tynamo app working using the archetype and then modifying it, I got
two model classes
- Person
- Local
File a (Tynamo) issue and I'll take a look.
Kalle
On Tue, Aug 31, 2010 at 6:31 PM, Paul Stanton wrote:
> I'm using the Tynamo tapestry-exception module, and for the most part it
> works great, however I've noticed that it doesn't seem to work for
> exceptions thrown during a 'setupRender' event
I'm using the Tynamo tapestry-exception module, and for the most part it
works great, however I've noticed that it doesn't seem to work for
exceptions thrown during a 'setupRender' event handler. These exceptions
are wrapped in a 'RenderQueueException' and load in the normal tapestry
exception