Articles, notes and random thoughts on Software Development and Technology
Red Hat have announced they are dropping their Red Hat Application Server, which was developed ontop of the Open Source app server JOnAS.
RedHat recently bought out the Open Source app server company JBoss, who are of course well known for their Java app server, so are looking to leverage their newly acquired assets.
OnJava.com have a detailed article giving an overview of getting started with the Google Web Toolkit.
I still haven’t had time to look at this yet, but it is definitely high on my list to check out.
ZDNet have a quick start guide in Ed Burnette’s blog entry showing you how to get started with the Google Web Toolkit (GWT).
The GWT was annouced this year at JavaOne and gives Java developers a pure Java approach to developing AJAX applications, by converting the Java code into HTML and Javascript. The GWT gives you a Java API which will be familiar to Java developers, and allows you to develop your app using the provided Java components, and then when ready generate the HTML and Javascript representation of the app with AJAX functionality. This is an awesome approach to avoiding Javascript development, which is hard to debug and develop (in comparison with Java and the rich IDE tools available).
TheServerSide.com have a question posted on their site this morning asking ‘Comparing EJB2 and JPA – why?’.
Ok so the technologies are now radically different and improved, and of course once you have seen the JPA api, there is obviously no turning back, providing you have a platform available that supports it.
These are two of the main reasons why it is important to make the comparison – the main reason – to educate developers and get them up to speed with the new EJB3.0 spec.
But surely this is such an awesome development and step forward for Enterprise Application development that any developer worth their salt will already be intimately familiar with the spec? Yes, of course it is awesome, and is how the EJB spec should have looked from day 1. The main problem I am seeing from working within my own Java developer community is that developers who will most likely be using EJB3.0 tomorrow are already entrenched in EJB2.x projects today – they are so busy working on current implementations that they have not had time yet to surface and see what is going on in the world. Yes they have heard of EJB3.0, have probably not heard of it referred to as JPA, and yes they would love to have time to read the spec and have time to prototype some apps, but they’re too busy right now.
It’s ‘the curse of the long running project’ – projects that were scoped and designed as long as 2 or even 3 years ago are still knee-deep in development implementing functionality on top of whatever technologies were chosen during the project’s inception. For 2-3 year old projects coming to a close, this is likely to be J2EE 1.3 and yes they are still using EJB2.x. If you’re lucky a long-running project may have in it’s contract the allowance to upgrade to latest API and technology releases along the way, but in most cases this is unlikely since this most likely does not buy the customer any inprovement in functionality, although may be desirable for long time maintenance.