Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of csethil@gmail.com designates
 209.85.132.250 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=rV4rVu0XSide4Ku5VdmRpNziOfvKL22VB8lhwzsLz6wbZJ1JThvweC/EHivvBP9Q4NaIvkOSj7I1JVkMKxyDQMVTL2Y1ypRVf4bUhxGrFmX1ycHJmYQMiJKpFNyyFOSUBw5K1Stx9d7JdStD//fgdsLnRrjeV7M6RYZJvuxlylM=
Message-ID: <e9115cfd0703011226v799e7103nc49aa3c73747c4fb@mail.gmail.com>
Date: Fri, 2 Mar 2007 02:26:49 +0600
From: "Thilina Gunarathne" <csethil@gmail.com>
To: axis-user@ws.apache.org
Subject: Re: [Axis2][Rampart] Rampart and SwA
In-Reply-To: <003801c75c14$d9a26b70$530214ac@RNelsestuen>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45E6C149.3020301@hpi.uni-potsdam.de>
	 <003801c75c14$d9a26b70$530214ac@RNelsestuen>

> Also, some research I did indicated (if I understood it correctly) that in
> Axis1.1.1 MTOM doesn't really work as an attachment - it ALWAYS will get
> encoded as Base64 embedded in the message - there was a config option
> previously (in Axis1.0) that allowed some sort of parameter to define binary
> data nodes, but it seems to have disappears.
AFAIK it is working as expected... Can you give us more specific
clues... Please use TCPMON to capture messages.. SOAPMonitor has a bug
which shows all the attachments as inline base64..

~Thilina
>
> -----Original Message-----
> From: Sebastian Roschke [mailto:sebastian.roschke@hpi.uni-potsdam.de]
> Sent: Thursday, March 01, 2007 5:04 AM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2][Rampart] Rampart and SwA
>
> Hi Thilina,
>
> thanks for the answer. I know that Rampart is able to secure MTOM
> messages. But utilizing MTOM is not usable for large messages. The
> amount of required memory is that high it is not usable for our
> project... I don't know the excact reasons for that, but in our
> performance tests the MTOM approach requires a lot of additional memory.
> The MTOM approach with file caching needs additional excecution time.
> Therefore we try to implement processing of large messages(more than
> 100MB) with SwA and java streams.
>
> Do you know where I can ask questions concerning the roadmap of specific
> components of Axis2? Maybe this is the wrong mailing list for such kind
> of question.
> But anyway, thanks for your answer...
>
> Regards,
> Sebastian
>
>
> Thilina Gunarathne schrieb:
> > Rampart has the capability to secure attachments send using MTOM..
> >
> > I'm not sure whether is there or planned support for SwA..
> >
> > Thanks,
> > Thilina
> >
> > On 3/1/07, Sebastian Roschke <sebastian.roschke@hpi.uni-potsdam.de>
> > wrote:
> >> Hello,
> >>
> >> due to memory efficiency I work with SwA to send messages based on java
> >> streams. Is there a possibility to secure such messages with Rampart? Is
> >> there any support for SwA in Rampart planned for future releases?
> >>
> >> Regards,
> >> Sebastian
> >>
> >>
> >>
> >
> >
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org