> well, the actual problem (taken apart from any ideas) is: a component > which is rendering its markup a wants to have another component > rending a id="" attribute as part of is markup and want to know that > id. So I also don't need them application wide, I just need a way to > tell a component to do this.
Ah, ok. Yeah, this is one of my outstanding feature requests too: http://sourceforge.net/tracker/index.php?func=detail&aid=1326849&group_id=119783&atid=684975 Maybe there is a way to fold this in with your behaviour idea (if we go for that; I haven't had the time to take a good look at it... sorry). > > AttributeModifier => sorry I was a bit angry about them :) I just > like to work in a more direct way with markup attributes, f.e. > expressing things like "add it only if its not there" in java code > instead of a flags like addAttributeIfNotPresent. But thats a matter > of taste :) :) Np. Maybe the behaviour idea would be more generalized than attribute modifiers. Let's see where that discussion leads us. Eelco ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
