This post originated from an RSS feed registered with Java Buzz
by dion.
Original Post: The case for high level components
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
David Hannson, of Rails fame, writes a case against high-level components.
Although we have definitely seen components NOT be successful in areas such as EJB (yeah, we can buy SO many vertical components), the web tier (apart from the displaytag ;), I don't think we should write off components in general.
There are many places where components make sense. They make sense in GUI development. Tapestry components work out great. In my experience, it depends on the contract and what you are trying to do. There are some items which you really don't need to tweak much, and if you do, it is there for you. However, it is hard to have ONE reusable component for "new WebCommunity().start()".
It is an art to choose what should be generized, what shouldn't, and how to give enough hooks to allow you to tweak the component.
Previous Topic
