BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Languages Content on InfoQ

  • An Update on Spring 2.0 Final

    Spring 2.0 was initially supposed to come out in June/July, why the delay? InfoQ interviewed the Spring team - based on massive community feedback, the team has chosen to delay the launch to Sept 26th in order work on asynchronous JMS capabilities, JPA, the new JSP form tag library, OSGi integration, documentation, and backwards compatibility.

  • From Java to Ruby: Risk

    "Ruby is risky" is a common perception. As Ruby on Rails moves closer to the mainstream, that risk will decrease. In this article, Bruce Tate examines the changing risk profiles for Java and Ruby from a managers perspective, examining Java's initial adoption and also common risk myths about Rails.

  • Grails + EJB Domain Models Step-by-Step

    Grails brings Ruby on Rails style productivity to the Java platform, built on the Groovy language and fully integrated with Java. This tutorial shows how to use Grails to quickly build a functional website around an existing EJB 3 entity bean domain model with very little code

  • Why Would a .NET Programmer Learn Ruby on Rails?

    .NET developer Stephen Chu gives us some insight into his transition to Ruby on Rails programming. Quote: "By being loyal to one technology stack, I am bound to unconsciously make biased decisions, which will ultimately hinder my ability to deliver business value."

  • Simplifying Enterprise Applications with Spring 2.0 and AspectJ

    This article reviews Spring AOP support in 2.0, and walks you through an adoption roadmap for AOP in enterprise applications, with plenty of examples of features that can be implemented simply using AOP, but would be very hard to do any other way.

  • Using Logging Seams for Legacy Code Unit Testing

    Using logging seams you can easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes.

  • Agile: The SOA Hangover Cure

    Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.

  • From Java to Ruby: Strategies for Pilots

    The Ruby on Rails revolution has been led by developers. Convincing management takes another kind of persuasion. A manager needs to understand the risks of adopting Ruby, the risks of snubbing mainstream languages like Java--even for one project--and the overall technical landscape of Ruby's capabilities.

  • Annotation Hammer

    Annotations in Java 5 provide a very powerful metadata mechanism. Yet, like anything else, we need to figure out where it makes sense to use it. In this article we will take a look at why Annotations matter and discuss cases for their use and misuse.

  • EJB 3 Glossary

    An essential glossary of new terms and concepts introduced in EJB 3. The glossary demystifies buzzwords like (IoC), Configuration by Exception, POJO, POJI, Dependency Injection, Embeddable Object, Interceptors, and more. This glossary will constantly be updated.

  • ESB Roundup Part two: ESB Use Cases

    This is the second part of InfoQ's ESB series, an exploration of Enterprise Service Bus, or ESB technologies. The focus is use cases required by companies deploying this technology, such as protocol bridging, security intermediation and service virtualization. The article references analyst commentary, survey research results and comments on part one of the ESB roundup.

  • Will the Enterprise change Ruby, or will Ruby change the Enterprise?

    Ruby is often criticized for lacking the features required for developing large applications and maintaining them over long periods of time with large teams. Are we missing something fundamental for widescale adoption of Ruby in the enterprise?

BT