SpringSource CTO Adrian Colyer talks to InfoQ about AspectJ. The interview explores how products such as Spring Roo are using AspectJ, and how ideas from AspectJ helped SpringSource improve the Groovy compiler inside Eclipse. Colyer also discusses SpringSource's two server offerings, dm Server and tc Server, OSGi and Scrum.
Chris Richardson discusses the evolving cloud computing landscape, cloud computing tools, differences between local machines and cloud-based virtual machines, Cloud Foundry offerings, deploying a Java application to Cloud Foundry, Cloud Foundry vs other cloud offerings, future Cloud Foundry developments, and the future of enterprise Java development.
This interview, conducted at QCon 2009, covers a wide range of topics beginning with a definition of OSGi and ending with an audience question about integrating OSGi into legacy application servers (like Websphere). In between Neil answers questions about the origins and evolution of OSGi, how OSGi compares to .Net modularization, and constraints on the use of certain Java libraries.
In this interview made by InfoQ’s Srini Penchikala, Rob Harrop talks about SpringSource dm Server, its OSGi based modularity and the advantages it offers. He also touches other adjacent topics like support for Java EE6, cloud computing, JMX, and others.
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
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.