Return-Path: X-Original-To: apmail-synapse-dev-archive@www.apache.org Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3397E10459 for ; Fri, 12 Apr 2013 07:53:02 +0000 (UTC) Received: (qmail 61809 invoked by uid 500); 12 Apr 2013 07:53:02 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 61586 invoked by uid 500); 12 Apr 2013 07:53:00 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 61566 invoked by uid 99); 12 Apr 2013 07:52:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 07:52:59 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mastershield2007@gmail.com designates 209.85.128.176 as permitted sender) Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com) (209.85.128.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 07:52:52 +0000 Received: by mail-ve0-f176.google.com with SMTP id ox1so2139162veb.7 for ; Fri, 12 Apr 2013 00:52:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=OlAi0g45414D2dscXBli2q8shJeS3nQOldr8F86qa5g=; b=lozE72pCjPHELNNnaNsCdZGHM6w7LhbeBfyLa4oSW6ioCeCdGAWa1hn2PULWgmvAym MkuWpGMiDgYHKUnfGy9hpmQguECGOTUkqtluQlGRZiRezb+En/CBp4Fs+BCB7rpgUfxm nvoLJ7OAjkqSWGXYTfyPgDJ4KMQl2KttZqY0YVqzTlfNTaAYu2sTPWgZz8bvsKqo8YNW ErF4TEmOdo2okZ61FBWMDg3ASGF37RmnTBZELdf6hsN/BUcrQMRDVC71HTmj68VPljVo sdXLk5kgMTF6pcCwjbDlWG2fXu2MUmaSwQX+1dRRgEsWU/+uy4mc8wq6ZWqsg+4f0AmZ H/4g== MIME-Version: 1.0 X-Received: by 10.220.221.210 with SMTP id id18mr7515635vcb.74.1365753151758; Fri, 12 Apr 2013 00:52:31 -0700 (PDT) Received: by 10.58.34.169 with HTTP; Fri, 12 Apr 2013 00:52:31 -0700 (PDT) In-Reply-To: References: Date: Fri, 12 Apr 2013 03:52:31 -0400 Message-ID: Subject: Re: Project Ideas For GSOC 2013 From: Udayanga Wickramasinghe To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=14dae9cdc18176282f04da252f69 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9cdc18176282f04da252f69 Content-Type: text/plain; charset=ISO-8859-1 Hi Isuru/Andreas , If we can compile a list/track possible changes for synapse on those special cases you have mentioned that would be great. As far as i am concerned i do not see this as a GSoC project . Having said that if we can cover some ground with consistant Axiom APIs (ie:- w.r.t. AXIOM-412 and others) across synapse and specifically if Isuru is willing to do that as a project , i am fine with that.. Regards Udayanga On Wed, Apr 10, 2013 at 3:39 PM, Andreas Veithen wrote: > The idea would be to implement the necessary changes in Axiom, Axis2 > and Synapse so that DOOM can be used end-to-end for the messages that > flow through Axis2 and Synapse. That has potential benefits for > scenarios that use WS-Security (because it avoids LLOM <-> DOOM > transformations in Rampart) or mediators that interact with frameworks > that support DOM. > > Of course, both Axis2 and Synapse use the Axiom API and not LLOM > directly, so one would expect that to work, but that is only theory. > E.g. in earlier Axiom releases, there was a major difference between > LLOM and DOOM with respect to the lifecycle of the OMFactory > instances, that made it virtually impossible do substitute LLOM with > DOOM without major code changes. This was only changed in the last > Axiom release (see AXIOM-412). The missing OMSourcedElement support in > DOOM is another issue. There are likely lots of other places where > Axis2 or Synapse depends on behavior specific to LLOM. > > Andreas > > On Tue, Apr 2, 2013 at 7:12 PM, Udayanga Wickramasinghe > wrote: > > Hi Isuru, > > Synapse already supports Axiom API which i think DOOM is a part of. What > > exactly do you mean by "Axiom DOOM Support for Synapse" ? > > Regards, > > Udayanga > > > > > > On Tue, Apr 2, 2013 at 4:35 AM, Isuru Ranawaka > wrote: > >> > >> Hi All, > >> > >> I am an undergraduate student of Computer Science and Engineering > >> department University Of Moratuwa. I would like to do a project for > GSOC . > >> One idea is to Axiom DOOM Support for Synapse. Is that idea is good > enough . > >> > >> thanks > >> isuru > > > > > > > > > > -- > > http://www.udayangawiki.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org > For additional commands, e-mail: dev-help@synapse.apache.org > > -- http://www.udayangawiki.blogspot.com --14dae9cdc18176282f04da252f69 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Isuru/Andreas ,
If we can compile a list/track poss= ible changes for synapse on those special cases you have=A0mentioned=A0that= would be great. As far as i am concerned i do not see this as a GSoC proje= ct . Having said that if we can cover some ground with consistant Axiom API= s (ie:- w.r.t.=A0AXIOM-412 and others) across synapse and specifically if Isuru is = willing to do that as a project , i am fine with that..

Regards
Udayanga


On Wed, Apr 10, 2013 at 3:= 39 PM, Andreas Veithen <andreas.veithen@gmail.com> w= rote:
The idea would be to implement the necessary= changes in Axiom, Axis2
and Synapse so that DOOM can be used end-to-end for the messages that
flow through Axis2 and Synapse. That has potential benefits for
scenarios that use WS-Security (because it avoids LLOM <-> DOOM
transformations in Rampart) or mediators that interact with frameworks
that support DOM.

Of course, both Axis2 and Synapse use the Axiom API and not LLOM
directly, so one would expect that to work, but that is only theory.
E.g. in earlier Axiom releases, there was a major difference between
LLOM and DOOM with respect to the lifecycle of the OMFactory
instances, that made it virtually impossible do substitute LLOM with
DOOM without major code changes. This was only changed in the last
Axiom release (see AXIOM-412). The missing OMSourcedElement support in
DOOM is another issue. There are likely lots of other places where
Axis2 or Synapse depends on behavior specific to LLOM.

Andreas

On Tue, Apr 2, 2013 at 7:12 PM, Udayanga Wickramasinghe
<mastershield2007@gmail.co= m> wrote:
> Hi Isuru,
> Synapse already supports Axiom API which i think DOOM is a part of. Wh= at
> exactly do you mean by "Axiom DOOM Support for Synapse" ? > Regards,
> Udayanga
>
>
> On Tue, Apr 2, 2013 at 4:35 AM, Isuru Ranawaka <irjanith@gmail.com> wrote:
>>
>> Hi All,
>>
>> I am an undergraduate student of Computer Science and Engineering<= br> >> department University Of Moratuwa. I would like to do a project fo= r GSOC .
>> One idea is to Axiom DOOM Support for Synapse. Is that idea is goo= d enough .
>>
>> thanks
>> isuru
>
>
>
>
> --
> htt= p://www.udayangawiki.blogspot.com

---------------------------------------------------------------= ------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org




--
http://www.udayangawiki.blogspot.com
--14dae9cdc18176282f04da252f69--