FpML Issues Tracker

181: AnyMessage should be Message in error handling

May 28, 2006

closed

Minor

Always

Documentation

Admin

mgratacos

Summary

In section 3.4.2 of the documentation, Error Handling, the message interaction is described using a message of type "AnyMessage". To be correct, this should be renamed as "Message". Any type that implements Message (therefore including its derived messages), would then be legal.

AnyMessage is the a description of the message and not its type.

Attachments

  • MessageRejection.gif

    • Notes:

  • mgratacos

    06/06/06 4:39 am

    The error is on section 3.2.4. We’ll fix the diagram.

  • mgratacos

    06/06/06 5:03 am

    The diagram has been corrected in subversion. See attached file. It will be published in the 4.2 Recommendation and 4.3 Working Draft.

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue