Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-2478

Incorrectly removing a parameter from the Message

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.2.3, 2.1.7, 2.2.4
    • 2.1.8, 2.2.5
    • None
    • Tomcat 6.0.18, Windows Server 2003. CXF 2.2.4.

    Description

      I've been having the following issue for a whole day already, and I'm debugging it: http://www.coderanch.com/t/466933/Web-Services/java/CXF-fails-serve-WebService

      I've got further ahead:

      in WrapperClassInInterceptor there is this code:

      (line 135 onwards)

      newParams = new MessageContentsList(helper.getWrapperParts(wrappedObject));

      List<Integer> removes = null;
      int count = 0;
      for (MessagePartInfo part : messageInfo.getMessageParts()) {
      if (Boolean.TRUE.equals(part.getProperty("messagepart.isheader"))) {
      MessagePartInfo mpi = wrappedMessageInfo.getMessagePart(part
      .getName());
      if (lst.hasValue(mpi))

      { newParams.put(part, lst.get(mpi)); }

      else if (mpi.getTypeClass() == null) {
      if (removes == null)

      { removes = new ArrayList(); }

      removes.add(Integer.valueOf(mpi.getIndex()));
      }
      } else

      { ++count; }

      }

      The parameters in "newParams" before the removes are removed are the correct params + one null at the end.
      Then index "1" is removed. BUT the param at Index 1 is correct. So perhaps the index is wrongly calculated. I don't have any more time to dig further into the generation of the index, so I'm just patching my version by commenting-out the removal part. I hope you can give me an update no this. Thanks

      Attachments

        1. roc_remedy_service.wsdl
          33 kB
          Bozhidar Bozhanov
        2. SOAPMessage.txt
          2 kB
          Bozhidar Bozhanov

        Activity

          People

            dkulp Daniel Kulp
            glamdring Bozhidar Bozhanov
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: