Hi All, Please I was wondering generally,
Are there any Performance Benefits in 1. Breaking a Wicket Page Down into many tiny components in seperate Java-HTML files thus simplyfing code and component reuse AGAINST 2. Coding all the UI components in one long, looooong:) WebPage Code which obviously always leads to spagetti convoluted code. I am asumming (2) will be faster because wicket will not be loading too many .HTML files in order to assemble one page even though optimizing code will become very difficult. Too many anonymous inner classes. Please does anyone have a take on this. Has anyone done a benchmark on this case. Thanks -- Aladejebi Ayodeji A., DabarObjects Solutions
