Tag: API design

Bloated JavaBeans™, Part II – or Don’t Add “Getters” to Your API

Posted on by lukaseder

I have recently blogged about an idea how JavaBeans™ could be extended to reduce the bloat created by this widely-accepted convention in the Java world. That article was reblogged on DZone and got quite controversial feedback here (like most ideas that try to get some fresh ideas into the Java world): http://java.dzone.com/articles/javabeans™-should-be-extended. I want to … Continue reading Bloated JavaBeans™, Part II – or Don’t Add “Getters” to Your API →

The good API design

Posted on by lukaseder

I've stumbled upon a nice checklist wrapping up API design guidelines. An extract: Favor placing API and implementation into separate packages Favor placing APIs into high-level packages and implementation into lower-level packages Consider breaking up large APIs into several packages Consider putting API and implementation packages into separate Java archives Avoid (minimize) internal dependencies on … Continue reading The good API design →