Re: Reading the MTOM/XOP attachment

[JordiCA <jo...@puck.eu>]

Hi,

I happen to be integrating exactly the same third-party service (the name of
the classes gave me the right clue) and found the same issue. The
DataHandler is not properly returning the binary file in the attachment,
that as you did, I confirmed it's being received in the logs.

First of all, THANK YOU SO MUCH for providing the 'squirrelly' work-around
to access the attachment. I was getting desperate trying to make this work
and already started thinking of dirtier solutions like accessing the
attachments through the logging system...
From your comments I understand that as long as the requests to this service
are done in a synchronous way accessing the response context should be safe
enough. I did a few tests and that seems to be the case... Could you
confirm?

Which solution did you finally apply? Did you manage to get the attachments
directly from the DataHandler?

in any case, thanks a lot!



--
View this message in context: http://cxf.547215.n5.nabble.com/Reading-the-MTOM-XOP-attachment-tp5764160p5768758.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Reading the MTOM/XOP attachment

[dolanp <do...@gmail.com>]

Hey there. Glad to hear I'm not the only one. No, unfortunately I never found
a way around it so the synchronous approach was what I used. I believe this
is probably some sort of CXF bug when combining MTOM/XOP and WSS4J.



--
View this message in context: http://cxf.547215.n5.nabble.com/Reading-the-MTOM-XOP-attachment-tp5764160p5768760.html
Sent from the cxf-user mailing list archive at Nabble.com.