[jira] Updated: (WICKET-1469) New Wicket tag 'wicket:for'

["Erik van Oosten (JIRA)" <ji...@apache.org>]

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

Erik van Oosten updated WICKET-1469:
------------------------------------

    Attachment: WICKET-1469-for-wicket-1.4.x.patch

Attachment WICKET-1469-for-wicket-1.4.x.patch can be applied to branch 1.4.x.

Supported:
 - "wicket:for" attribute, value refers to any component
 - during rendering the "for" attribute is generated with as value the referred component's markup id
 - referred component's will automatically render its markup id when it is located /after/ the wicket:for attribute in the markup stream

Not supported:
 - referred component will /not/ automatically render its markup id when it is located before the wicket:for attribute in the markup stream

Any clues on how to support the latter are much appreciated. The alternative is to remove auto rendering of markup ids completely.

> New Wicket tag 'wicket:for'
> ---------------------------
>
>                 Key: WICKET-1469
>                 URL: https://issues.apache.org/jira/browse/WICKET-1469
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>    Affects Versions: 1.3.2
>            Reporter: Jan Kriesten
>            Priority: Minor
>             Fix For: 1.5-M1
>
>         Attachments: WICKET-1469-for-wicket-1.4.x.patch
>
>
> This often happens during my daily work:
> You create a form with labels and corresponding input fields. As it is now, you have to bind all those Labels and FormComponents together with some "boilerplate" code within Java.
> I'd like to suggest the following enhancement Wicket tag:
> <label wicket:for="username" wicket:messge="key">default message</label>
> where wicket:for contains the referenced wicket:id

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