camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul McCulloch <pkmccull...@gmail.com>
Subject Re: CXF component attachment support for POJO not implemented as specified
Date Fri, 21 Nov 2014 17:26:33 GMT
I should probably add that I am trying to handle 'anonymous' attachments -
they are not referenced in the WSDL at all.

On 21 November 2014 09:36, Paul McCulloch <pkmcculloch@gmail.com> wrote:

> This test cases are for MTOM though I think. I need to use SOAP with
> Attachments for my service.
>
> Thanks again,
>
> Paul
>
> On 21 November 2014 05:41, Willem Jiang <willem.jiang@gmail.com> wrote:
>
>> The attachment is mapped by CXF into the MessageContentList.
>> Here is an unit test[1] in camel-cxf for it, you can find the wsdl file
>> here[2]
>>
>>
>> [1]
>> https://github.com/apache/camel/blob/master/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/mtom/CxfMtomConsumerTest.java
>> [2]
>> https://github.com/apache/camel/blob/master/components/camel-cxf/src/test/resources/mtom.wsdl
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.iteye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On November 21, 2014 at 2:48:50 AM, Paul McCulloch (pkmcculloch@gmail.com)
>> wrote:
>> > Thanks for getting back to me Willem. I'm afraid I don't understand your
>> > reply though! What do you mean by "the POJO parameter list"?
>> >
>> > I thought you might mean that the attachments get added as additional
>> > entries to the MessageContentList - but that doesn't seem to be the
>> case. I
>> > had a look through the source and can't find anywhere that the incoming
>> CXF
>> > attachment is propagated to the POJO, message or exchange.
>> >
>> > My use case is implementing a WSD first SOAP service supporting Soap
>> > with attachments on incoming messages.
>> >
>> > Thanks,
>> >
>> > Paul
>> >
>> > On 20 November 2014 04:25, Willem Jiang wrote:
>> >
>> > > Hi Paul,
>> > >
>> > > For the POJO, we don’t want to export the attachment from message to
>> the
>> > > user as the user can access the attachment from the POJO parameter
>> list.
>> > > If we expose the attachment throw the message API for the POJO data
>> > > formate, it could cause some trouble if the user makes some changes
>> through
>> > > the message and POJO parameter list at same time.
>> > >
>> > > --
>> > > Willem Jiang
>> > >
>> > > Red Hat, Inc.
>> > > Web: http://www.redhat.com
>> > > Blog: http://willemjiang.blogspot.com (English)
>> > > http://jnn.iteye.com (Chinese)
>> > > Twitter: willemjiang
>> > > Weibo: 姜宁willem
>> > >
>> > >
>> > >
>> > > On November 20, 2014 at 12:53:17 AM, pkmcculloch (
>> pkmcculloch@gmail.com)
>> > > wrote:
>> > > > I agree that the work for CAMEL-7181 doesn't cover all cases.
>> Looking at
>> > > the
>> > > > current source I see a couple of issues:
>> > > >
>> > > > 1) populateExchangeFromCxfRequest(Exchange, Exchange) doesn't check
>> > > > MTOM_ENABLED - it never includes attachments for POJOs
>> > > >
>> > > > 2) populateCxfResponseFromExchange(Exchange, Exchange) - the same
>> issue.
>> > > >
>> > > > Can someone re-open the JIRA task? Or should I log a new one?
>> > > >
>> > > > I'm quite happy to make the fixes. What's the best format to submit
>> the
>> > > fix
>> > > > - patch or pull request?
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Paul
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > View this message in context:
>> > >
>> http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
>> > > > Sent from the Camel - Users mailing list archive at Nabble.com.
>> > > >
>> > >
>> > >
>> >
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message