You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Filip Balas <fb...@IMVProjects.com> on 2005/03/09 00:17:51 UTC

Stale link problem...

I have a 2 components and a page.

The page on its own works with all 
actionlinks going to where they are
supposed to go.

Now I have a component 'foo'.
'foo' works when it is embeded in the
above page.

Now I have a third component 'bar'
that is nested inside 'foo'.

When the page renders, everything
looks normal.  The functionality of 
the nested component works.

However, when I click on any of 
the actionlinks in the page (which
previously worked) I recieve a stale
link page.  It seems that the nested
component somehow scrambled up
the mappings of the actionlinks because
all of the links are there when I mouse
over the link.

What happens is this:
I have 3 links: A,B,C

When I click on A I recieve the error:
Action id 1 matched component B, not A

When I click on B I recieve the error:
Action id 2 matched component C, not B

When I click on C I recieve the error:
Action id 3 matched component A, not C

So somehow, by adding the component
to the page... tapestry's internals got 
sacrambled.  Does anyone have any ideas
for how to debug this?

Filip