Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Rule your SOA
with CentraSite
standards-based
registry/repository
Create REST
-enabled Web Apps
with Project Zero
from IBM.
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.
In this part of the Struts 2 migration series, Struts committer Ian Roughely looks at a real application and compares the Struts and Struts 2 implementations, identifies how to convert actions, configuration changes, and what parts of the codebase don't need to be converted.
Struts committer Ian Roughely explains, from the perspective of a Struts developer, the high level architecture, basic request workflow, configuration semantics and differences in the action framework in the new Struts 2 (formerly WebWork). Armed with this knowledge, migrating an application of any size from Struts to Struts 2 should be simplified.
Mainsoft recently released version 2.0 of Mainsoft for Java EE (formerly known as Visual Mainwin), and also released a whitepaper which showed that a .Net-based application which was cross-compiled to run on Java EE using Mainsoft for Java EE performed as well as or better than the original .NET-based application did in several areas. InfoQ spoke with Mainsoft CEO Yaacov Cohen to learn more.
HostedQA, JIRA, Confluence, and Jive Forums all have implemented frameworks to manage changes to db schema's and data migrations between subsequent versions of their products. Pat Lightbody proposes that all enterprise apps should include an upgrade framework and provides some best practices.
This book argues that for SOA to succeed we must move our thoughts away from the implementation technologies and towards the "what" of the business. Using a straight-forward, pictorially driven, methodology the book explains who to discover what the business services really are and how to construct an overall business service architecture.
