Hi,
Did you specify the optimize parts element "OptimizeParts" with the
xpaths?
Did you specify the mtom policy as <wsoma:OptimizedMimeSerialization/> ?
What version of rampart are u using?
If the problem exist, please file a JIRA.
Regards,
Dimuthu
On Tue, 2007-07-17 at 15:00 +0530, Thilina Gunarathne wrote:
> May be rampart guys can answer this better...
>
> Thanks,
> Thilina
>
> ---------- Forwarded message ----------
> From: Giao <[EMAIL PROTECTED]>
> Date: Jul 16, 2007 9:19 PM
> Subject: MTOM & WS Securit
> To: [EMAIL PROTECTED]
>
>
> Hi,
>
> We use Axis 1.3 and SWA on the server side in
> production. We're starting to develop using Axis2
> because of MTOM support and .NET client compatibility.
>
> We have successfully tested both Axis2 and .NET/WSE
> 3.0 clients against the MTOM Sample app.
>
> Once I enable security with
> "ServiceClient.engageModule(new QName("rampart")) the
> outgoing message has the attachment in-line (in XML
> envelope) and
> base64 encoded, rather than has the expected
> <xop:Include href="cid..."> Also the content length
> now is 33% larger because of base64 encoding. It
> still works, although the capacity is now limited to
> about 20MB before the server gets an out of memory
> error. Previously I was testing with about 50MB.
>
> I didn't see any mention in the OASIS WSS v1.0 specs
> about MTOM.
>
> Is there any way around this limitation?
>
>
> Thanks in advance,
> Giao
>
>
>
>
> ____________________________________________________________________________________
> Got a little couch potato?
> Check out fun summer activities for kids.
> http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
