tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1600) A component that is defined inside a <t:block> does not appear as an embedded component, causing page-load exceptions on the event handlers for the embedded component
Date Tue, 09 Aug 2011 20:56:27 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081921#comment-13081921
] 

Howard M. Lewis Ship commented on TAP5-1600:
--------------------------------------------

I'm having trouble reproducing this.

Here's my test case:


<html t:type="Border" xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd">

    <t:delegate to="block:zen"/>

    <t:block id="zen">

            <t:actionlink t:id="goForBroke">go for broke</t:actionlink>

    </t:block>


</html>


package org.apache.tapestry5.integration.app1.pages;

import org.apache.tapestry5.alerts.AlertManager;
import org.apache.tapestry5.ioc.annotations.Inject;

public class ComponentInsideBlockDemo
{
    @Inject
    private AlertManager mgr;

    void onActionFromGoForBroke() {
        mgr.info("Go For Broke Clicked");
    }
}


It works perfectly.

> A component that is defined inside a <t:block> does not appear as an embedded component,
causing page-load exceptions on the event handlers for the embedded component
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1600
>                 URL: https://issues.apache.org/jira/browse/TAP5-1600
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> Reported from ProQuest, but not yet verified.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message