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] Assigned: (TAP5-553) Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
Date Thu, 05 Mar 2009 17:53:58 GMT

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

Howard M. Lewis Ship reassigned TAP5-553:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Tapestry should include a new binding prefix, "clientId:", that extracts the clientId
of a component
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-553
>                 URL: https://issues.apache.org/jira/browse/TAP5-553
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> It is quite frequently desirable to get a component (that implements ClientElement) and
extract the component's clientId property.  Currently you have to inject the component into
the page to expose it as a property to extract the clientId.

-- 
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