-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 It could also be argued that having enough stuff in your pages that needs testing separate from validating mark up structure and such violates separation of concerns. Your pages and panels really should just drive the UI with your business logic in another, separately testable layer.
Igor Vaynberg wrote: > On 11/7/06, craigdd <[EMAIL PROTECTED]> wrote: >> >> >> I don't know, I think this really violates the concept of separation of >> concerns, which wicket seems to really market. > > > the separation of concerns is in the fact that the template contains no > logic. so template designers can easily work with it, and coders can > work on > java stuff. > > take servlets - designers cannot work on markup because it is output > completely using java code > > take jsp - designers cannot work on markup because it is far too easy for > them to break stuff since it is littered with logic. > > in wicket the markup simple and logic/code free. designers can still break > stuff but breaking the sync between java and html component hierarchy but > they cannot break logic, so it is much safer. and after working with wicket > markup for a day a designer can get used to not breaking things. > > You should be able to as a >> developer, develop and test the behavior of a component without having to >> rely on the html to be written. > > > this is where we disagree. as i said, imho, a component consists of a few > facets that are interconnected, not just java. > > -igor > - -- Justin Lee http://www.antwerkz.com AIM : evan chooly Skype : evanchooly -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) iD8DBQFFUU3vJnQfEGuJ90MRA6EoAJwJDlQJ3ajzqUHzBJ/mMaqN+k5FgQCeJPAM GmLRK8885yj5zfMnorqSz0U= =HgEn -----END PGP SIGNATURE-----
