Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: management
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      112

      Description

      It appears that unmarshaling/marshaling message elements is very costly.
      This processing must be reduced. Reducing this processing has a non negligeable
      impact on the current API of major classes (Message, Management, SOAP...).
      Unmarshalling is done each time a piece of data is get from Message class.
      Marshaling and unbind of existing element is done each time a piece of
      information is set to the Message. This is required when you want the internal
      SOAPMessage to be in sync with the wrapper. Do we really want this perpetual
      synchronization?

      We should be able to get/set information without doing any marshal/unmarshal
      processing and finally ask for a SOAPMessage. Currently the Message.getMessage()
      returns the actual internal SOAPMessage. It should be replaced by a SOAPMessage
      createMessage() that will create a SOAPMessage based on what was previously get/set.
      As said, it changes the way these core classes are behaving.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            wiseman-issues
            Reporter:
            jfdenise
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: