Another interesting fact is, the response is successfully processed when we
invoke the producer (webservice) directly. The error only coming only when
we communicate the producer via ESB.
On Wed, May 18, 2011 at 5:37 PM, Anil Atyam wrote:
> Thanks Andreas.
>
> I will pursue that option. Meanwh
Thanks Andreas.
I will pursue that option. Meanwhile, do you see any other leads causing this
issue?
Does the response has to have a base64Binary element?
Is it possible to restrict MTOM to only request and not the response?
Appreciate if you can answer these questions.
Thanks
Anil Atyam
Ph:
We don't provide support for commercial products based on Axis2. You
should use the correct channels for this, i.e open a PMR with IBM
support.
Andreas
On Wed, May 18, 2011 at 22:29, Anil Atyam wrote:
> Thanks Andreas for the response. We are using IBM WebSphere application
> server version 7.0
Thanks Andreas for the response. We are using IBM WebSphere application
server version 7.0 with latest fix packs. So, I assume IBM using latest and
greatest AXIS2 and AXIOM. If not the greatest, they must be using 1.2.8.
I have tried my best to locate the information and couldn't find it. I am
pas
On Wed, May 18, 2011 at 19:19, Anil Atyam wrote:
> Folks
>
> I appreciate if you can help with the following issue we are struggling to
> resolve.
>
> We @ National Rail Road Corporation implementing a solution where we send
> Itinerary as PDF attachment to the passenger's email. To do so, we are
Folks
I appreciate if you can help with the following issue we are struggling to
resolve.
We @ National Rail Road Corporation implementing a solution where we send
Itinerary as PDF attachment to the passenger's email. To do so, we are using
MTOM enabled Web Service which sends to request to a thi
