Canfield
Subject: Re: Component parameters-unintended persistent binding
To: "Tapestry users"
Received: Tuesday, October 19, 2010, 8:06 AM
You were probably hitting the page url for every image with the image path
as context to the page.
On 18 Oct 2010 23:41, "Jeshurun Daniel&
You were probably hitting the page url for every image with the image path
as context to the page.
On 18 Oct 2010 23:41, "Jeshurun Daniel" wrote:
> I've finally figured out the cause of the problem but is just really
> weird. Turns out the problem was being caused by a CSS class name!
>
> This is
I've finally figured out the cause of the problem but is just really
weird. Turns out the problem was being caused by a CSS class name!
This is the code from the breadcrumb component:
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
${currentMenuItem.text}
Hi Howard,
Thanks for the quick reply, I really need help with this.
I have three page classes, Index, Page1 and Page2
Template for Index:
Template for Page1:
Template for Page2:
I have three components, a layout component, a menu component and a page
component.
This is the source for the
This may not be entirely your issue, but the t:if test parameter takes
in property bindings, so I believe that is why it would be calling the
getters on the mainMenuId even if it were blank/null on the second page.
What happens if you have the test parameter link to a boolean method
that handle
I'm confused from your description. I'm sure its something minor, but
we'd need to know the version you are using, plus more details from
your .tml and .java files to figure out what's going on.
On Mon, Oct 18, 2010 at 12:19 PM, Jeshurun Daniel wrote:
> Hi everyone,
> This is a really strange pr
Hi everyone,
This is a really strange problem I'm having with component parameters and I've
spent a whole day on this and I'm still clueless.
I have three components, a custom layout component, a menu component and a
breadcrumb component. The menu and breadcrumb components are contained within
