On 9/7/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > none of the code youve written so far counts unless are are writing an app > against 2.0 because the interfearing features here are only available in > 2.0. and even then its a very young concept and code.
So which features are they then? Anything else other than the ability to read markup (attributes)? And why/ when does the markup that the component is attached to switch? Isn't this only the case when e.g. the parent depends on markup of a child? And is it always the component itself we want to protect, or is it the parent? > what we are talking about here is support moving by default - probably > breaking things > or denying moving by default - yes extra interface which might or might not > be api bloat Well, the 'propably breaking thing' is where we don't agree on, as I think it's not a common case at all (or read will be if you like). And even if a component got initialized using some attribute of the markup it's attached to and that markup changes somehow (though I don't see how this happens by switching the parent), even that doesn't mean it is suddenly in an illegal state. Only if the component developer decides to, which he can by rechecking attributes e.g. when rendering. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
