Tag: java

Firestar software are suing RedHat, the owner of JBoss and the Hibernate ORM technology, for infringing on it’s patent regarding Object Relational Mapping technology.

Analysts are speculating why they chose to single out RedHat, and why this point in time – ORM solutions have been around for a number of years. They could have chosen to go after Oracle for Toplink, a ORM solution they acquired from WebGain, or any one of a number of implementations of the now standardized JSR220 EJB3.0 Java Persistence API, which is based on Hibernate.

CEO of Sun Microsystems, Jonathan Schwartz, has stated that he will soon reveal how much Sun makes from selling Java related services. It has long been thought that Sun has missed a golden oportunity with Java for making some serious cash, and assumed by giving away Java for free it makes money from companies buying it’s hardware on which they run Java based systems. Schwartz did not give a date but will reveal the information soon.

There has been a lot of noise about this recent announcement – Sun have decided, apparently of their own accord without any buy-in from the JCP committee for Java the 6.0 JSR, that they will bundle the Apache Derby database engine in the 6.0 SDK.

This seems like an odd decision, as many have been commenting, and has recieved a lot of negative press so far. As far as I can tell this is only an addition to the SDK and will not be bundled in the JRE. This is good so it won’t be included in an already large download for the JRE, but it means that if a developer chooses to use Derby ‘because it’s there’ they can’t rely on it being available on their target platform. So what benefit has this added? If it is only targetted at developers, I am sure (I sincerely hope) that if a developer is capable of downloading and installing the SDK or their favorite IDE that they are more than capable of downloading any one of a number of freely available open source databases?

Struts 1.x as we know it is pretty much at the end of the road. Since JSF was introduced and now standardized as the web framework of choice in Java EE 5.0, as tool support increases for many there will be no other choice – use JSF for the web framework.

However the Struts community didn’t pack up and go home, they have been busy developing in many (confusing?) different directions. Timothy O’Brien’s blog entry on the OnJava.com site outlines these different directions.

First up is the continuation of the Struts 1.x codeline, now being referred to as the Struts Action 1 framework. This FAQ on their site says that development is continuing, however with so many other options out there, including JSF as well as other the other Struts projects, I think it would be foolish to go with Struts 1.x if starting a new project today. Why? Yes it’s tried and tested, but there are now better options available.

Next – the merging of the WebWork project and it’s framework with Struts has given birth to Struts Action 2 Framework. I’m not familiar with this codeline at all, but understand this will be what was formally known as WebWork, as a new version, 2.3.

Next comes Struts Shale. Shale is not Struts. It is a framework built on top of JSF, to ease JSF development and fill the gaps where the Struts Shale developers feel that JSF is lacking. Shale is described as what Struts would have originally been, if the developers had known then what they know now.

And the choices don’t end there – there are now many more Web Application frameworks out there than there have ever been. Gavin King’s Seam framework is getting a lot of press, again, building on top of JSF and offering features such as conversation support that are not handled in JSF by default. There are plenty of other choices all that have their own pros and cons, and implemented using different approaches, some command pattern based like Struts, some event based like Tapestry. If you are looking to choose a web framework today, I would do some homework and checkout these alternatives, since defaulting to Struts is possibly not the best choice anymore.