The problem as I see it is that the JiBX code generation doesn't
currently support the special AXIOM elements that handle attachments.
However, I haven't looked into the details of how the general Axis2 code
generation handles attachments, so it's possible that this can actually
operate in the situation you described without any cooperation from
JiBX. Have you tried this out to see what happens?
- Dennis
Alexander Grivnin wrote:
Hi Dennis,
Thanks for clarifications.
Basically we want to enable attachments for the operations whose parameters are of primitive types and do not contain any mapped classes. In this case it sounds like JiBX serialization mechanism is not invoked and the attachments in this case supposed to work, no?
Thanks for your help,
Alex
________________________________
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Fri 1/5/2007 11:35 PM
To: [email protected]
Subject: Re: [Axis2] Jibx with Attachments
Hi Alex,
Not at present, at least without doing something like hand-modifying the
generated message receiver and client stub. This is something I'm
planning to add support for in JiBX 1.2.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Alexander Grivnin wrote:
Hello,
Is it possible to work with attachment using Jibx mapping? Most
importantly we are looking for an ability to send attachments in the
response message.
Thanks in advance,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
