InfoQ Homepage Articles
-
Migrating to Struts 2 - Part III
In this third and final part of the Struts 2 migration series, Struts committer Ian Roughely completes the migration of a Struts app to Struts 2, by migrating the user interface - jsps & tags. This series teaches Struts 2 architecture & the differences in request processing as well as how to configure a Struts2 app and combine actions and JSP's.
-
The Lost Art of Separating Concerns
In a short article, well-known REST proponent Mark Baker claims the default, Web services-based approach to SOA development fails to properly separate concerns, and describes how the more generic interface used in Web architecture leads to an improvement.
-
Interview: Using Agile for SOA
Recently, Digital Focus documented their experience using Agile to tackle SOA for Federal Home Loan Banks. The incremental approach included adopting an SOA platform that could grow as the SOA application portfolio grew, and getting frequent feedback from customers and developers. InfoQ interviewed both the client and the author of the experience report on the project, and business-IT alignment.
-
Casestudy: IP Telephony Integration
This case study takes at Litescape's IP telephone integration solution, from requirements through an architectural overview of their Java and .NET implementation, and then zooming in some interesting technical aspects of their project including phone integration with WebEx/LiveMeeting, integration between Java/.NET interop, HTTP vs. IPC communication between systems installed on the same machine.
-
Compass: Integrate Search into your apps
Many applications have the user requirement to search domain entities. SQL implementations quickly develop complexity issues as multiple fields are added. Java applications explore the Lucene indexing API but implementing functionality using it can prove time consuming. This tutorial walks through the process of using the Compass API to simplify this integration.
-
Incorporating Enterprise Data into SOA
The majority of today's SOA design techniques are centered around definition of services. They use service-oriented decomposition, based on the business processes, enterprise business/functional model, required long term architectural goals and reuse of the existing enterprise functionality. This article takes a more data centric approach...
-
Making AspectJ development easier with AJDT
Aspect Oriented Programming (AOP) can be used to solve a number of today's application requirements but can also be intimidating for developers when getting started. A new article by Matt Chapman, AJDT Project Lead, shows how AOP development with the popular AspectJ library can be made easier using the Eclipse AspectJ Development Tools (AJDT) plugin.
-
Experience Report: Beginners and Experts All Benefit in Open Space
Agile conferences are receiving an influx of novice teams and managers, and some suggest that new conferences should be organized for these beginners. To the contrary, this report from XPday Montreal suggests that mixing up expertise levels creates a valuable experience for all.
-
Railway Story: SimpleTicket
A 5-year old, Dallas-based company named Spur is gaining attention and kudos within Ruby on Rails circles. Earlier this week it announced a new release of its popular GPL'd IT support tool named SimpleTicket. Managing Partner Alexander Muse was kind enough to share the story of SimpleTicket with InfoQ.
-
ESB Alternative - Article removed at the author's request
This article was removed from InfoQ at the author's request.
-
Spring.NET - QnA
InfoQ had a chance to sit down with Aleksandar Seovic and Mark Pollack the co-creaters of Spring.NET. Spring.NET is an application framework that brings AOP, a Dependency Injection container and data access framework to .NET. It is not a complete port of Spring to .NET yet it preserves the tenets of Spring.
-
Adopting Agile Development Practices: Using Patterns to Share our Experiences
Agile adoption often proves challenging. Participants at a recent OpenSpace event focused on the dynamics of adoption rather than the structure that results from adoption. The resulting patterns are part of an effort to compile Agile adoption patterns answering: "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?"