[ 
https://issues.apache.org/jira/browse/TAPESTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard M. Lewis Ship closed TAPESTRY-2388.
------------------------------------------

    Resolution: Fixed

Thanks for the patch; I wrote my own that deferred allocating the id until the 
getClientId() method is first called.

> The Any component should implement the ClientElement interface, and allocate 
> a unique client id as necesssary
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2388
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2388
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0, 5.0.11, 5.0.12
>            Reporter: Chris Lewis
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.0.12
>
>         Attachments: any-clientelement.patch
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> It would be nice if the Any component implemented ClientElement, so that for 
> example, mixing in arbitrary javascripts could be done so in a simple way (by 
> injecting their container as a ClientElement, and getting the DOM id).

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to