Steve Landry, Paul Hill, and Jim Repa were in attendance.
MIT SASH submitted for review, based on SourceLabs SASH2 stack but modified to be compatible with certain existing MIT applications so teams do not have to port backward or lose compliance with some specifications.
- SourceLabs version comes with multiple tools to do the same job. The Working Group had an open question as to whether they should keep those tools in the stack even though they would not be able to properly support them or provide examples.
- The Steering Committee recommends keeping all the SASH2 jars but flagging "undersupported" tools in our documentation.
- The move to FreeMarker makes the MIT stack 100% SASH, or not using any Sun J2EE standard. Everyone is OK with this since the full set of "sash" style tools is the way the industry is going.
Working Group Request for Messaging Services and ESB
- The steering committee members agreed that "messaging" and "ESB" are nebulous concepts to the Working Group will have to contribute some time to ISDA to work out real requirements. Many products labelled as "messaging" or "ESB" will probably not solve real MIT problems.