Decoupling business process and business data in WebSphere Process Server: A new twist to the MVC pattern
From the developerWorks archives
Date archived: November 22, 2016 | First published: June 01, 2011
This article describes a development pattern separating the life cycle of a business process and its corresponding business data. This approach provides strong decoupling of the respective life cycles, increasing robustness to cope with inevitable changes. The process keeps only a minimal set of information, while the actual business data is represented by managed Java Persistence API entities in the logic layer. The same entities are exchanged as detached entities between the logic and user interface layers in the form of data transfer objects. After introducing the various layers of the architecture, the article leads you through the steps of implementing a basic application based on this pattern in WebSphere® Integration Developer V7.0 and WebSphere Process Server V7.0.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.