Menu

#432 Wrong parsing of IMETHODCALL request

closed-fixed
3
2006-11-11
2006-08-24
Endre Bak
No

Some attribute and node names in this code don't
correspond to names which is used by the XML builder
to build up an IMETHODCALL request.

I think that this part of code is never called by a
dependent application, because the parsing of the CIM
request is the task of the CIMOM, not the client. But
this "feature" can be used for testing the output XML
stream of client requests.

If some dependent application uses this "feature", the
correction of this bug can break it!

Discussion

  • Endre Bak

    Endre Bak - 2006-08-24
    • assigned_to: nobody --> ebak
     
  • Endre Bak

    Endre Bak - 2006-08-24

    fix

     
  • Endre Bak

    Endre Bak - 2006-08-24
    • priority: 5 --> 3
    • status: open --> open-fixed
     
  • lupusalex

    lupusalex - 2006-09-25
    • status: open-fixed --> pending-fixed
     
  • lupusalex

    lupusalex - 2006-09-25

    Logged In: YES
    user_id=1363884

    The community review is completed and we received no substantial
    critisism. Therefore the patch has been approved and merged into
    the "HEAD" branch. The next release will pick it up.

     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     
  • lupusalex

    lupusalex - 2006-10-27
    • status: closed-fixed --> pending-fixed
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     
  • lupusalex

    lupusalex - 2006-11-13

    Logged In: YES
    user_id=1363884

    The patch was picked up by release 1.3.1 therefore this bug will
    be closed.

     

Log in to post a comment.