also note that everything might mean /components/ in your parameters... what would that even mean? seems like any params like this would have to be free of component tags.
another thing to point out is that the wicket component tag that you are parameterizing can already have a body.
Jonathan Locke wrote:
yeah, i'd like to see some compelling use cases for this first.
Juergen Donnerstag wrote:
maybe this param tag would be handy in some cases:
<wicket:params name = "myProperty">My completely free text that can contain everything</wicket:params>
Does that mean that more than <wicket:params >, one after another must be possible? How else would you pass a second parameter like that to the component?
Juergen
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
