Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-53

Missing contentId for methods 'addAttachment' in SoapMessage

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0 M2
    • Fix Version/s: 1.0 M3
    • Component/s: Core
    • Labels:
      None
    • Environment:
      All platforms

      Description

      It is now impossible to set a Content-Id to a SOAP attachment with Spring-WS.

      The methods to improve are (org.springframework.ws.soap.SoapMessage) :

      • Attachment addAttachment(File file) throws AttachmentException;
      • Attachment addAttachment(InputStreamSource inputStreamSource, String contentType);

      They will be replace (I think) by :

      • Attachment addAttachment(String contentId, File file) throws AttachmentException;
      • Attachment addAttachment(String contentId, InputStreamSource inputStreamSource, String contentType);

      Thanks for this improvment.

        Activity

        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        I've added a setId() method to the Attachment interface, currently only implemented by SAAJ.

        Show
        arjen.poutsma Arjen Poutsma added a comment - I've added a setId() method to the Attachment interface, currently only implemented by SAAJ.
        Hide
        gvasquez Gonzalo Vasquez added a comment -

        I'm having an issue with the addAttachment(String contentId, DataHandler dataHandler) method in SAAJ, as attachments get appended to the response with their assigned contentId, but no reference contentId appears in the root part of the response.

        I've tested this in JBoss 4.2 and IBM WAS 6.1, same problem on both environments.

        Show
        gvasquez Gonzalo Vasquez added a comment - I'm having an issue with the addAttachment(String contentId, DataHandler dataHandler) method in SAAJ, as attachments get appended to the response with their assigned contentId, but no reference contentId appears in the root part of the response. I've tested this in JBoss 4.2 and IBM WAS 6.1, same problem on both environments.

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            bcornouiller Bruno Cornouiller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: