Role in IT decision-making process:Align Business & IT GoalsCreate IT StrategyDetermine IT NeedsManage Vendor RelationshipsEvaluate/Specify Brands or VendorsOther RoleAuthorize PurchasesNot Involved

Work Phone:

Company:

Company Size:

Industry:

Street Address

City:

Zip/postal code

State/Province:

Country:

Occasionally, we send subscribers special offers from select partners. Would you like to receive these special partner offers via e-mail?YesNo

Your registration with Eweek will include the following free email newsletter(s):News & Views

By submitting your wireless number, you agree that eWEEK, its related properties, and vendor partners providing content you view may contact you using contact center technology. Your consent is not required to view content or use site features.

By clicking on the "Register" button below, I agree that I have carefully read the Terms of Service and the Privacy Policy and I agree to be legally bound by all such terms.

Open-Source Leader Highlights Technologies for Developers to Watch

In a keynote address at TheServerSide Java Symposium, Rod Johnson, the founder of the open-source Spring application framework, offered developers tips on how to make Java and J2EE a stronger alternative to Microsoft's .Net.

LAS VEGAS—Rod Johnson, an outspoken member of the open-source community, rallied Java developers to wave their Java flags high but to look beyond Java and hone their business and communications skills as they look for new opportunities in a world where Java and Microsoft Corp.s .Net reign as the top platforms for developers.

Johnson, who is based in London and is the founder of the open-source Spring application framework, showed a kindler, gentler side during a keynote at TheServerSide Java Symposium here Friday.

Though Johnson has been critical of J2EE (Java 2 Platform, Enterprise Edition), he said he now sees it as the premier platform for development, and he gave an audience of developers advice on technologies to watch and opportunities to pursue, and tips on how to proceed to make Java and J2EE a stronger alternative to Microsofts .Net.

"J2EE today is in a very healthy state, with ongoing innovation and successful execution," Johnson said. "I am much more optimistic about J2EE today than at the first TheServerSide Java Symposium in 2003."

At the outset of his talk, Johnson said that "neither I nor any of my colleagues will be dressing up as film characters," taking a crack at JBoss Inc. CEO Marc Fleury, who with members of his staff, dressed up as the Joker and other villains from the Batman comic strip and movies.

Touting J2EE, Johnson said, "project success is now much more likely, much more predictable. J2EE is well-placed to take on Microsoft and .Net." Years before, Johnson said he considered .Net much more of a threat.

In addition, Johnson listed several technologies for developers to watch, including the Inversion of Control and dependency injection design patterns; unit testing and TDD (test-driven development); O/R (object/relational) mapping; post struts 1.x Web technologies such as JavaServer Faces, Spring Model-View-Controller and Tapestry, and value-add Web technologies such as Apache Beehive; and the rich client space.

Johnson also told developers to hone their skills that bring leverage, such as frameworks and methodologies, and to "look beyond Java" and work on communications skills and business skills.

"One key element to success is framework-oriented development," he said. "You choose a set of technologies, decide which is appropriate and you use it. This is a huge gain for developers. This is something that means the death of the in-house framework."

Meanwhile, Johnson said TDD is becoming more widespread and widely adopted because it can be done with smaller teams.

Johnson also questioned the notion of applying standards for every technology. Speaking on the recent skirmish regarding Java persistence, Johnson said, "What would have happened if O/R mapping had not been standardized in Java? We wouldnt have lost two to three years with entity beans and we wouldnt have wasted six to 12 months with the JDO/EJB3 [Java Data Objects/Enterprise JavaBeans] war."

Indeed, he said, "Clients are much less interested in the spec issue than we are. Standardization here is essentially a way of imposing some peoples choices on others. There is no ideal one-size-fits-all thing."