Who Would be Brazil In The Java World Cup?
Not Sun or Oracle, but SpringSource, according to their CEO Rod Johnson; a recent survey and work on java specs with Google supports his opinion
SpringSource triples its revenue
So, in that Java World Cup, who would Johnson’s SpringSource be? “In the software World Cup we want to be Brazil,” Johnson said. “We want to be the team people like to watch.”
And, according to Evans Data, people do tend to watch and use SpringSource. A survey taken at the end of 2008 indicated that 73 percent of organisations doing Java development said they currently used or planned to use the Spring Framework within two years.
Moreover, on June 2, SpringSource announced its most successful financial year up to April 30, 2009. The company more than tripled its support revenue from the previous financial year while achieving a series of milestones that both demonstrate SpringSource’s leadership position in the business Java industry and its success delivering strategic value to customers, partners, IT operations professionals and developers, Johnson said.
JSR-330 Proposed with Google
In addition, Johnson said that the “dependency injection JSR” which SpringSource is involved in with Google; JSR-330: Dependency Injection for Java, is set to be ratified in a matter of days. “We propose to maximise reusability, testability and maintainability of Java code by standardising an extensible dependency injection API (application programming interface),” the JSR entry said.
Bob Lee of Google and Johnson will lead the specification team. The JSR pulls from the Spring Framework and Google’s Guice.
According to the JSR-330 description of the technology:
“Existing approaches configure a dependency injector using XML, annotations or plain Java code. That injector is then used to construct objects and inject dependencies into them. This standard will provide a core API that can be driven at build and run time by higher-level configuration mechanisms such as XML and annotations. Objects configured using the various higher-level mechanisms will be able to freely depend on each other since the mechanisms will share a common foundation.”
Meanwhile, addressing the “Angry Man” issue, Johnson chuckled and said that it is actually mistaken, but that if indignation about the unnecessary complexity that plagued enterprise Java some years back makes him an “angry man”, then he accepts the label. That indignation led to the Spring Framework and other lighter weight, less complex technologies for enterprise Java developers, he said.
Since talking to eWeek, the SpringSource Google co-sponsored JSR-300 has in fact been passed.
