tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Zeigler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-680) 'Any' component didn't render id attribute
Date Sat, 02 May 2009 15:39:30 GMT

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

Robert Zeigler commented on TAP5-680:
-------------------------------------

By design, components only render a clientId if "getClientId" is called on the component sometime
during the server-side dom render.

You can do this easily with a simple mixin:

public class ForceClientId {

    @InjectContainer
     private ClientElement element;

    @BeginRender
    void ensureId() {
        element.getClientId();
    }
   
}


And then in your component:
<t:any .... t:mixins="ForceClientId"/>

If that doesn't solve your issue, then there's a genuine issue, and you can re-open this.

> 'Any' component didn't render id attribute
> ------------------------------------------
>
>                 Key: TAP5-680
>                 URL: https://issues.apache.org/jira/browse/TAP5-680
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.1.0.4
>            Reporter: Nikita Koksharov
>            Priority: Critical
>
> Any component not rendering id attribute if clientId defined,
> <input t:type="Any" t:clientId="someid" type="hidden"/>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message