Please let me know if you come up with an answer. I
am also using MTOM from an Axis2 client. (Axis2 1.1.1
and Rampart 1.1. I am sticking with these version
because everything else works. I know Axis2 1.2 did
not work with Rampart 1.1 so I stopped testing other
combinations.)
As soon as I call
'ServiceClient.engageModule("rampart")' Axis2 seems to
ignore the statement
'Options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE)' and puts the attachment as
base64 encoded within the SOAP message.
I have been avoiding stepping through the Axis2 and
Rampart source code to debug. This would either help
me identify a property I'm not setting, or I'd find
that I have to recompile the Axis2/Rampart code,
something that I would not like to do.
Thanks in advance.
Giao Nguyen
--- Jorge Fernandez <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I would like to know how does Rampart work with
> MTOM. I see that when using Rampart, MTOM elements
> are included as strings in the SOAP message instead
> of sending them outside the message as MIME parts,
> even if I don't do any operation with them (not
> signature, nor encryption), but these MIME parts
> appear empty in the HTTP message. Why is that?
>
> Does optimize parts something about that? I don't
> understand much about this parameter.
>
> If anybody could give me a hint about this, that
> would be great.
>
> Thanks,
>
> Jorge Fernández
>
>
>
>
> ---------------------------------
>
> Sé un Mejor Amante del Cine
> ¿Quieres saber cómo? ¡Deja que otras personas te
> ayuden!.
>
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
