Home > Uncategorized > Have you well enough exploited Java’s static typing?

Have you well enough exploited Java’s static typing?

Iterators, XML and Properties file for configuration, JDBC hacks were all considered as a pre-2003 developer standards. But really lot has changed since JDK5.0 (2004 itself). But it took years for me to catch-up.

Now when I see piece of java code still using Iterator, Enumerators, Too much of XML, No usage of generics, suddenly I couldn’t digest. May be I am too complacent and assuming others didn’t know materials like http://stackoverflow.com/questions/15496/hidden-features-of-java.

In reality, every developer who often does coding always shown interest in smart-coding. Especially when we aware something does the smart work, We are proud to use and share with co-developers. After all Java itself evolving just by sharing in open-source, and not depending on single place for all innovation to happen.

Quite a big list of features (JDK 5.0 & JDK 6.0 features) were not well utilized by most of the java developers.

Let me begin with one topic and it is *Annotations*

Long long ago, so long ago (Weblogic 5.x), annotations were used inside ejb’s, I used to see them as un-touchable alien. Because I never considered them as a java code for unknown reasons. When XDoclet gained momentum in open source community, mostly they were solving struts, ejb, blah.. framework issues. But no solution for any of day-to-day coding issues.

Later when I was override’ing a method in sub-class, which was not actually doing what I expect. It took alomost hour to identify a typo in my code. How could JAVAC can read my brain. Then I realized, there is a way to capture What I think about a method using @Override, from then JavaC does ensure that really it does what i meant to do.

My relationship with EJB and spring – both were hate relationship, Spring xml’s are not ensured at compile time and EJB’s bloated and heavy weight. JPA was a kind of win-win, it make sure things are checked at compile time and not at run-time. If needed can be decorated using EJB’s.

Now I am exploring how @Annotation can do dependency injection, without XML configurations. Nowadays I really love @Annotations. But still I wish I could see more suggestion from you how you exploited power of Annotation in your projects.

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: