Petals BC SOAP

Too many attachments put in the JBI exchange

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.4.2
  • Fix Version/s: 4.4.3
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload, with content-type 'application/xop+xml') of the multi-part HTTP message is also put in the JBI exchange.

    POST http://localhost:8084/petals/services/EDMService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_0_26937373.1483606877952"
SOAPAction: "http://petals.ow2.org/bc/rest/edm/archiver"
MIME-Version: 1.0


------=_Part_0_26937373.1483606877952
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@soapui.org>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edm="http://petals.ow2.org/bc/rest/edm">
   <soapenv:Header/>
   <soapenv:Body>
      <edm:archiver>
         <edm:library>my-library</edm:library>
         <edm:document><inc:Include href="cid:602465885939" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></edm:document>
      </edm:archiver>
   </soapenv:Body>
</soapenv:Envelope>
------=_Part_0_26937373.1483606877952
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: <CDE-avatar_105x105.jpg>
Content-Disposition: attachment; name="CDE-avatar_105x105.jpg"

<----File content---->

    It is not needed to put the root part as attachment in the JBI exchange.

    Show
    When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload, with content-type 'application/xop+xml') of the multi-part HTTP message is also put in the JBI exchange. 
    POST http://localhost:8084/petals/services/EDMService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_0_26937373.1483606877952"
SOAPAction: "http://petals.ow2.org/bc/rest/edm/archiver"
MIME-Version: 1.0


------=_Part_0_26937373.1483606877952
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@soapui.org>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edm="http://petals.ow2.org/bc/rest/edm">
   <soapenv:Header/>
   <soapenv:Body>
      <edm:archiver>
         <edm:library>my-library</edm:library>
         <edm:document><inc:Include href="cid:602465885939" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></edm:document>
      </edm:archiver>
   </soapenv:Body>
</soapenv:Envelope>
------=_Part_0_26937373.1483606877952
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: <CDE-avatar_105x105.jpg>
Content-Disposition: attachment; name="CDE-avatar_105x105.jpg"

<----File content---->
    It is not needed to put the root part as attachment in the JBI exchange.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 5 Jan 2017 - 10:01:50 +0100
Field Original Value New Value
Fix Version/s 4.4.3 [ 10684 ]
Priority Major [ 3 ]
Description When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload) of the multi-part HTTP message is also put in the JBI exchange.
It is not needed to put the root part as attachment in the JBI exchange. 		When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload) of the multi-part HTTP message is also put in the JBI exchange.
{code}
POST http://localhost:8084/petals/services/EDMService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_0_26937373.1483606877952"
SOAPAction: "http://petals.ow2.org/bc/rest/edm/archiver"
MIME-Version: 1.0


------=_Part_0_26937373.1483606877952
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@soapui.org>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edm="http://petals.ow2.org/bc/rest/edm">
   <soapenv:Header/>
   <soapenv:Body>
      <edm:archiver>
         <edm:library>my-library</edm:library>
         <edm:document><inc:Include href="cid:602465885939" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></edm:document>
      </edm:archiver>
   </soapenv:Body>
</soapenv:Envelope>
------=_Part_0_26937373.1483606877952
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: <CDE-avatar_105x105.jpg>
Content-Disposition: attachment; name="CDE-avatar_105x105.jpg"

<----File content---->
{code}

It is not needed to put the root part as attachment in the JBI exchange.
Christophe DENEUX made changes - Thu, 5 Jan 2017 - 10:02:25 +0100
Description When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload) of the multi-part HTTP message is also put in the JBI exchange.
{code}
POST http://localhost:8084/petals/services/EDMService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_0_26937373.1483606877952"
SOAPAction: "http://petals.ow2.org/bc/rest/edm/archiver"
MIME-Version: 1.0


------=_Part_0_26937373.1483606877952
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@soapui.org>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edm="http://petals.ow2.org/bc/rest/edm">
   <soapenv:Header/>
   <soapenv:Body>
      <edm:archiver>
         <edm:library>my-library</edm:library>
         <edm:document><inc:Include href="cid:602465885939" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></edm:document>
      </edm:archiver>
   </soapenv:Body>
</soapenv:Envelope>
------=_Part_0_26937373.1483606877952
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: <CDE-avatar_105x105.jpg>
Content-Disposition: attachment; name="CDE-avatar_105x105.jpg"

<----File content---->
{code}

It is not needed to put the root part as attachment in the JBI exchange. 		When WS client invoke a wen-service exposed by the BC SOAP with MTOM-optimized attachments, these attachments are put in the JBI exchange but the root part (the one containing the XML payload, with content-type '{{application/xop+xml}}') of the multi-part HTTP message is also put in the JBI exchange.
{code}
POST http://localhost:8084/petals/services/EDMService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_0_26937373.1483606877952"
SOAPAction: "http://petals.ow2.org/bc/rest/edm/archiver"
MIME-Version: 1.0


------=_Part_0_26937373.1483606877952
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@soapui.org>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edm="http://petals.ow2.org/bc/rest/edm">
   <soapenv:Header/>
   <soapenv:Body>
      <edm:archiver>
         <edm:library>my-library</edm:library>
         <edm:document><inc:Include href="cid:602465885939" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></edm:document>
      </edm:archiver>
   </soapenv:Body>
</soapenv:Envelope>
------=_Part_0_26937373.1483606877952
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: <CDE-avatar_105x105.jpg>
Content-Disposition: attachment; name="CDE-avatar_105x105.jpg"

<----File content---->
{code}

It is not needed to put the root part as attachment in the JBI exchange.
Christophe DENEUX made changes - Thu, 5 Jan 2017 - 10:02:39 +0100
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Thu, 5 Jan 2017 - 10:02:44 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 5 Jan 2017 - 11:23:25 +0100

Fixed in trunk

Show
Christophe DENEUX added a comment - Thu, 5 Jan 2017 - 11:23:25 +0100 Fixed in trunk
Christophe DENEUX made changes - Thu, 5 Jan 2017 - 11:23:25 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
2m 14s
1
Christophe DENEUX
Thu, 5 Jan 2017 - 10:02:39 +0100
Open Open In Progress In Progress
5s
1
Christophe DENEUX
Thu, 5 Jan 2017 - 10:02:44 +0100
In Progress In Progress Resolved Resolved
1h 20m
1
Christophe DENEUX
Thu, 5 Jan 2017 - 11:23:25 +0100

People

Dates

  • Created:
    Thu, 5 Jan 2017 - 10:00:25 +0100
    Updated:
    Thu, 5 Jan 2017 - 11:23:25 +0100
    Resolved:
    Thu, 5 Jan 2017 - 11:23:24 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.