This is a little esoteric, but I believe in it fully… Read the rest of this entry »
The Education of the Architect
January 13th, 2009A bit about WADL (Revised)
August 23rd, 2007In today’s high-tech world there is a growing need to create a simpler way to describe web-based applications. In the past one would use a WSDL to describe such application. One competing project put forth from Sun is Web Application Description Language [WADL] Read the rest of this entry »
Technology and Architecture – Walls ARE Important
July 3rd, 2007One of the first notations made in my notes from the ZapThink session Read the rest of this entry »
Introduction to HttpUnit
June 13th, 2007In today’s application development environment it is standard practice to build unit tests for each object being developed. Unit testing is increasingly more and more popular in Java due to the many open-source unit testing frameworks available. However, this type of testing becomes more difficult when the application is Web based or contains EJBs because of the dependency on application servers, servlet containers and EJB containers. Read the rest of this entry »
Useful Resources in WSDL Design for Complex Payloads
June 7th, 2007Some useful articles and best practices information for WSDL design in systems with complex XML schemas. Read the rest of this entry »
ZapThink LZA Reviewed
May 24th, 2007ZapThink launched LZA (Licensed ZapThink Architect) Boot Camps in early 2007 to provide a SOA credential and matched training. The Boot Camps were intended to provide both a common, objective understanding of SOA to practicing Enterprise Architects and the chance to obtain a credential from a qualified and respected third party (ZapThink). Read the rest of this entry »
SOA – Wrap and Replace the Squeaky Wheel
May 20th, 2007Many SOA advocates refer to the implementation of SOA as “wrap and replace” rather than “Rip and Replace.” createTank has determined through experience that a more refined description might sometimes be helpful — that of “wrap and replace ‘the squeaky wheel.’” This description is usually more acceptable to developers and management alike, as it highlights the possibility that a great deal of legacy code may not need to be rewritten at all (or at least not immediately). Read the rest of this entry »