tag:blogger.com,1999:blog-27876765.post5390219149711742155..comments2024-03-20T13:37:39.909+01:00Comments on Day to day stuff: More portlet woesErik van Oostenhttp://www.blogger.com/profile/15976519439979651010noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-27876765.post-41051504617545273132006-09-08T14:25:00.000+02:002006-09-08T14:25:00.000+02:00+1 interesting
How true, how true.
Being the colle...+1 interesting<br />How true, how true.<br />Being the collegue I can just say that I am more than disappointed with the portlet specification and the portlet engine pluto especially.<br /><br />True, portlets have been around for a while and maybe that is why it seems to be soooo old fashioned, architecture wise. Additionally, most people immediately associate 'portlet' with 'reusable component' which means 'gooooooood'. <br />That is not only not necessarily true but 'overdoing' it seems to be creating a more dependent and tightly coupled system than you would have without portlets.<br /><br />Oh well, at least I can support Erik on the wicket-issue: This is one wicked (pun intended :) framework. The more I do with it the more I come to love it.<br />Although you really have to get used to writing web applications like normal Java apps.<br /><br />But hey ... there is always something, right?! ;)Chehttps://www.blogger.com/profile/18073666483469758994noreply@blogger.com