"Transformation" has become an increasing popular topic among Progress' Application Partners and end user customers with responsibility for their own legacy applications. This blog will be an on-going discussion of topics related to transformation including, but not limited to, different types of transformation, transformation strategies, transformation tools, and anything else which might help a company with a legacy ABL application decide how and what to modernize.
"Transformation" has become a popular term in the ABL for various kinds of application modernization -- moving to a new User Interface (UI), implementing a Service-Oriented Architecture (SOA), evolving toward the OpenEdge Reference Architecture (OERA), and other projects directed toward upgrading old versions of legacy ABL applictions. Today's ABL is just not the same language it was back 15-20 years ago when many ABL applications were first written and our ideas about good architecture have, if anything, evolved more than the language.
This category will be used to discuss principles of building UI components, sample UI component code, and helper classes for ABL UI.
It may be necessary or appropriate for us to subdivide this are according to the UI technology since contributions might deal with a variety of technologies.
This category will be used to discuss principles of building UI service components, sample UI service component code, and helper classes for UI services.
UI services are components which run on the server and provide an interface between clients and the business logic layer. They contain no UI themselves. It is likely that some will be specific to a given UI and will serve to isolate the business logic layer from the specifics of the particular UI. Some may be UI independent.
This category will be used to discuss principles of building enterprise service components, sample enterprise service component code, and helper classes for enterprise services.
This category will be used to discuss principles of building business logic components, sample business logic component code, and helper classes for business logic.
This category will be used to discuss principles of building data access components, sample data access component code, and helper classes for data access.
For initial background reading, consult OERA Strategies: Object-Oriented or Not?
The OpenEdge Reference Architecture (OERA) describes an overall structure and pattern for the architecture of modern applications, but does not in itself specify any particular implementation. Progress Software (PSC) has generated a series of whitepapers over recent years which discuss various aspects of this architecture with some sample code, but this code is limited in scope and there is no pretense of it illustrating production-ready techniques. More recently, PSC introduced AutoEdge, an “application example” meant to illustrate one way in which OERA principles might be applied in a real application, but it too is built on a number of simplifying assumptions and does not pretend to offer production ready code on which customers might build real systems without significant further work.
Matkaraportti
Progress Technology World for Europe, Middle East and Africa 2006
Athens, Greece 10 – 12 September 2006
En ollut ainoa - suomalaisista enkä muunmaalaisista - joka olin positiivisesti yllättynyt tämänvuotisen Progress-käyttäjäpäivien sisällölliseen antiin. Siis toisin kuin viime vuonna Lissabonissa, jossa odotukset ylittivät tarjonnan.