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 (pkmccull...@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. >
