Skip to main content

Do you primarily think of yourself as a...

J2ME developer
5% (29 votes)
J2SE developer
55% (348 votes)
J2EE developer
41% (258 votes)
Total votes: 635

Comments

Web Services, but in J2SE code

It's interesting that although the Java I'm writing is exposed entirely through web services, I'm working entirely with J2SE technologies. I'm slowly replacing pieces of the back end of an old ASP application, called from the ASP controller tier through SOAP. Of course there is a servlet container involved, but using Apache Axis, I need to know nothing of the J2EE APIs to do my daily work. I have worked with Servlets, JSP, JMS, and a little EJB in the past, but not at all on this project.. I really like the POJO -> Web SAervice mapping going on. I write my APIs to test cases developed in Java without worrying about how to expose them to the ASP code, then, through the magic of Axis, have a WSDL. It feels almost like cheating. :-)

What about plain old Java developer?

After all, Java is just Java and the difference between a J2EE and a J2ME developer has mostly to do with the APIs they know and use most frequently.

Even between two J2EE developers this can vary a lot. For instance, some J2EE developers are really good at JSP, others are better with EJB and/or web services, some are even experts primarily in build and deployment.

What we all have in common is that we are most effective and efficient when we know the core language and J2SE APIs very well.

What about plain old Java developer?

I agree with you. Additionally, I am not fond of the emphasis on "editions". I think it takes our eye off of the ball. I also think that the emphasis on editions has create silos and may have prevented or slowed functionality from appearing across those editions.

I remember when I first started learning Java 2D Java 3D and I thought that some of the technologies would be useful on devices. Asking when we could expect to see those capabilities on J2ME was considered an odd question. Ironically, the people who found it odd were gamers and it winds up that games on devices is pretty hip after all.

Java is Java. Editions only matter to me when I think about how an application needs to be deployed. On a device? On a desktop? Will I need a server?

Just my opinion.