JavaOne, and things

Its Saturday and I’m sitting in a coffee shop down the street from my house watching it rain. Kerry is in Boston this week visiting some friends so I’m bacheloring it up (an by that, I mean playing on my laptop). Work is going good, but very busy. We are getting ready to release our product, which is exciting, but like all projects in the world, it is coming down to the last wire. I’m really excited because I think we are going to show our market something they have never seen before, which was our goal from the beginning.

Other than work I’ve just been playing around. I attended JavaOne in San Franciscoa few weeks ago and had a ball. Anyone who says Java is dead just doesn’t know what they are talking about. You’d be amazed the places it is popping up, servers, wireless, embedded apps. Lockheed Martin (airplane and missile people) were showing an un-manned aircraft whose internal controls ran Java (Realtime VM of course). I’m excited about Java 1.5 and I can’t wait to start using it.

One big topic at JavaOne was EJB 3.0, which several vendors have released. Basically, it takes a lot of the overhead out of using EJB, thanks to Java 1.5 annotations. You can take a regular java class, and by tagging it with annotations, turn it into a EJB. The container you are deploying in takes care of doing everything else. Of course xdoclet has been doing this for a while. Same thing with Entity Beans, which is nice because some of the mapping files for those can get pretty bad. The funny thing, is that when we saw Hibernate a few years ago, some people said this should be the next ejb3, well, it pretty much is. POJO based mapping.

Other cool technologies were Groovy (java scripting) and JXTA

JXTA is a java P2P framework where you can map an application on top of any network topology. I think this technology is very important because of the way the industry is going. As rich-clients become more and more intense, the client-server model becomes un-manageable. Customers no longer want to interface with the system, they want the system to interface with them. A good example is a stock program. As a client, I don’t want to poll the server for changes, I want the server to notify me in real-time about changes. This becomes more complex as you throw NAT firewalls and try doing this over a WAN. JXTA was created to overcome this problem. So take a look at it, if you don’t your competitors will!