Is it worth my while to submit a patch to support inbound anonymous
attachments, I guess with some configuration option to enable the feature?
Paul
On 21 November 2014 at 17:26, Paul McCulloch pkmccull...@gmail.com wrote:
I should probably add that I am trying to handle 'anonymous' attachments
If we cannot access the attachment from the the MessageContentList in POJO
model, the solution sounds good.
--
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
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.ji...@gmail.com wrote:
The attachment is mapped by CXF into the MessageContentList.
Here is an unit test[1] in camel-cxf for it,
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 pkmccull...@gmail.com wrote:
This test cases are for MTOM though I think. I need to use SOAP with
Attachments for my service.
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 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
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)
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
Hi Willem,
thank you.
I have two comments:
1) It is used in three methods, one for producer and two for consumer. I
believe it should be changed in all the methods so that it works in both
directions.
/populateExchangeFromCxfResponse(Exchange camelExchange,
Hi,
the CXF description states:
http://camel.apache.org/cxf.html#CXF-AttachmentSupport
http://camel.apache.org/cxf.html#CXF-AttachmentSupport
Attachment Support
/POJO Mode:
Attachments are propagated to Camel message's attachments since 2.1. So, it
is possible to retreive attachments by
It makes sense, I just filled a JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-7181
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/)
11 matches
Mail list logo
