In this panel discussion from QCon San Francisco, several influential leaders of the software development community discussed and debated the future of the Java language and APIs based upon the lessons we have learned from the past. Topics included static versus dynamic languages, removing code from Java, forking the JVM, and the next big programming language.
JRuby project lead Charles Nutter discusses how he got involved with JRuby, Sun's involvement with JRuby, how JRuby fits into enterprise-level web applications, the possibility of a friendly fork of the OpenJDK source code, reasons for switching to JRuby, the future of JRuby, Spring and JRuby, and the Ruby community as a whole.
In this interview from QCon San Francisco, SpringSource CEO Rod Johnson discusses the origins and philosophy of Spring, the Spring Portfolio, Spring Web Flow, Spring Batch, Spring.Net, the partnership with Tasktop Technologies, and community involvement and utilization of Spring.
InfoQ recently sat down with Peter Kriens of the OSGi Alliance to learn more about OSGi. Kriens discussed OSGi's origins in the mobile space, it's integration with Eclipse, the current integration work with Spring, and the future R5 specification. He also discussed the ongoing debate over OSGi and JSR 277, and gave his perspective on what an ideal solution would be for modularity at the JVM level.
At The Spring Experience conference, InfoQ caught up with Patrick Linskey of BEA to discuss the current status of the Apache OpenJPA project. Linskey explains where OpenJPA came from, how it fits into the Object\Relational Mapping space, the differentiating features that OpenJPA provides, the JPA specification, and future plans for OpenJPA.
Keith Donald goes in depth on Spring Web Flow, which solves the problem of orchestrating control navigations within a web application in Spring MVC, Struts, and JSF. Keith talks about how to design workflows in web apps and technical details such as how the flows are fault tolerant and how they integrate into web frameworks.
In this interview co spec lead Mike Keith discusses the current state of EJB 3. He covers how the community has drove the development of the EJB 3 spec as well as the praises and criticisms that have developed along the way. Keith also comments on the evolution of the specification to be work better with pojo's and embrace newer ideas such as dependency injection.