Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 34233 invoked from network); 15 Jun 2008 15:07:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jun 2008 15:07:28 -0000 Received: (qmail 37237 invoked by uid 500); 15 Jun 2008 15:07:27 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 37191 invoked by uid 500); 15 Jun 2008 15:07:27 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 37180 invoked by uid 99); 15 Jun 2008 15:07:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Jun 2008 08:07:27 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ruwan.linton@gmail.com designates 209.85.142.184 as permitted sender) Received: from [209.85.142.184] (HELO ti-out-0910.google.com) (209.85.142.184) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Jun 2008 15:06:37 +0000 Received: by ti-out-0910.google.com with SMTP id y6so1821767tia.18 for ; Sun, 15 Jun 2008 08:06:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=oFRxKlSUTIpRW9WBLmOOsjZpaJ7VT/uhbDWwpXD28MA=; b=BGMbB+oNp2LKCbt9YEx2t9jU/O+sS/Z+ou8GxF418Uj1bmT0PUdYuU6jx5NwMb3ZMP QfM/jqnm9PIw40FNq1paXc/iKNQr2HnS+jILu1w8APOMnMkwvaJ76guGFbbsqwRSzF+i enVv8Or10AGWYGIZlVDWNw5MukDH6glSxbvRI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=sEUCyD/RIhM2InSdCukb8TvT7kJeRhAZoiuTvF3G9C3gSgKVgmkG00l6BNCBbyvFmt pBueN/NUID/rvYMQwx33GYfbtNYoOK2KY+PxZ+ErqaQLhDGec7krwbUVgy8hq6tZSvRK h8Lyz2n2E8S5tTYc+MzKiTK/RpY9DYfkw7hIM= Received: by 10.110.84.3 with SMTP id h3mr3488621tib.48.1213542413533; Sun, 15 Jun 2008 08:06:53 -0700 (PDT) Received: by 10.110.86.17 with HTTP; Sun, 15 Jun 2008 08:06:53 -0700 (PDT) Message-ID: <672a01200806150806m11fb5798w2c1251f8b34d6f5@mail.gmail.com> Date: Sun, 15 Jun 2008 20:36:53 +0530 From: "Ruwan Linton" To: axis-dev@ws.apache.org Subject: Re: Extensions to Axis2/Java deployment engine In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7601_18833571.1213542413528" References: <48526AFC.9020104@wso2.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_7601_18833571.1213542413528 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Saminda, > > ================================================= > > In Synapse point of view. > > 1. Mediators can be written as OSGi bundles. What is the value addition? > When you start the bundle, the proper factory is called and build the > relevant object model. Even now it does very correctly ;-) > > > 2. Different version of same mediator is highly possible. i.e two mediator > can live in two different class spaces. Why do one need two versions? Do you expect the functionality to be different? In which case any way those are two mediators :-) > > > 3. You will be able to remove Sun service providers facility of loading > extension to bundles, which will be support in all Java implementations. We can do the same without OSGi > > > 4. Synapse guys like embedded devices ? I didn't get this point at all, can you please explain what you meant here? I think axis2 should provide the flexibility to use OSGi or be with the one that we have now. For example Synapse community does not want to be OSGi then we should be able to get the behavior that axis2 has now with the next versions as well. There fore I don't think it is good to do changes to the kernel which affects the current behavior of axis2. I really like deepal's suggestions and we should try to support OSGi features while keeping the current behavior and we can release a different artifact of Axis2 which supports OSGi. Also just wanted to make sure, what is the advantage of being OSGi with Java 7 which promises to provide versionning via JAM (Java Application Modules) Thanks, Ruwan > > > Thank you! > > Saminda > > > On Fri, Jun 13, 2008 at 6:11 PM, Asankha C. Perera > wrote: > >> Saminda >> >>> Main aspect of OSGi is version and modularity >>> >> Can you list the top 5 advantages for Axis2 end users (who develop >> services, or develop clients that consume services), and the top 5 >> advantages for those who embed Axis2 (such as Apache Synapse etc). I think >> this would be very valuable information for me to consider your suggestion, >> and assess the impact on Apache Synapse >> >>> I am really appreciate if Axis2 folks comment on prior. >>> >> Looking forward to your reply to comment further >> >> asankha >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org >> For additional commands, e-mail: axis-dev-help@ws.apache.org >> >> > > > -- > Saminda Abeyruwan > > Senior Software Engineer > WSO2 Inc. - www.wso2.org > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/ ------=_Part_7601_18833571.1213542413528 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Saminda,

=================================================

In Synapse point of view.

1. Mediators can be written as OSGi bundles.

What is the value addition?
 
When you start the bundle, the proper factory is called and build the relevant object model.

Even now it does very correctly ;-)
 


2. Different version of same mediator is highly possible. i.e two mediator can live in two different class spaces.

Why do one need two versions? Do you expect the functionality to be different? In which case any way those are two mediators :-)
 


3. You will be able to remove Sun service providers facility of loading extension to bundles, which will be support in all Java implementations.

We can do the same without OSGi
 


4. Synapse guys like embedded devices ?

I didn't get this point at all, can you please explain what you meant here?

I think axis2 should provide the flexibility to use OSGi or be with the one that we have now. For example Synapse community does not want to be OSGi then we should be able to get the behavior that axis2 has now with the next versions as well.

There fore I don't think it is good to do changes to the kernel which affects the current behavior of axis2. I really like deepal's suggestions and we should try to support OSGi features while keeping the current behavior and we can release a different artifact of Axis2 which supports OSGi.

Also just wanted to make sure, what is the advantage of being OSGi with Java 7 which promises to provide versionning via JAM (Java Application Modules)

Thanks,
Ruwan
 


Thank you!

Saminda 
   

On Fri, Jun 13, 2008 at 6:11 PM, Asankha C. Perera <asankha@wso2.com> wrote:
Saminda

Main  aspect of  OSGi  is version and modularity
Can you list the top 5 advantages for Axis2 end users (who develop services, or develop clients that consume services), and the top 5 advantages for those who embed Axis2 (such as Apache Synapse etc). I think this would be very valuable information for me to consider your suggestion, and assess the impact on Apache Synapse

I am really appreciate if Axis2 folks comment on prior.
Looking forward to your reply to comment further

asankha


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




--
Saminda Abeyruwan

Senior Software Engineer
WSO2 Inc. - www.wso2.org



--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/ ------=_Part_7601_18833571.1213542413528--