Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-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 7FF2772AD for ; Tue, 27 Sep 2011 00:44:23 +0000 (UTC) Received: (qmail 43609 invoked by uid 500); 27 Sep 2011 00:44:23 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 43560 invoked by uid 500); 27 Sep 2011 00:44:23 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 43552 invoked by uid 99); 27 Sep 2011 00:44:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Sep 2011 00:44:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.59] (HELO smtp104.prem.mail.sp1.yahoo.com) (98.136.44.59) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 27 Sep 2011 00:44:16 +0000 Received: (qmail 19018 invoked from network); 27 Sep 2011 00:43:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=rJNnyj5z/dUmluV5nzn6T+Btbn0/YaNdE9c4McTAA9vpT9IFZ2QN/+iYuq7oDBjYW2vmmiUoqQL1WmV3IyFVJLTx61uKa3M+tBbtTTm+Pxhqsp10obHa1YEFAMkAP7Q4VRbb+jXo95T31IWbPxye1VZciG76Q1q/5dWx5kLlx/w= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1317084235; bh=7utJXUdsj1sL68K1TGu5gcBfuw//sykuOhgxS696ZKs=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer; b=sz0VV9JUV63fnO3UlzgQMC7z3bH7cL9foUn6636/3fVmPq/4BReXfodznMt+OfXIbt2DGcjsCNsmp62RunU75PYLah3zU5G5ImnYEBEEbMF3UvE9HuXX+cYmLhryZTh+deoFEjV2qH060qjtXcH7qOdkDmXtLhdHq2GRbuw8Dqs= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: fSuF7vcVM1ks81NN70jW3y5aCk8iGr7HZH5o_I55MLH6UW1 cp.09EAZD67coQIq04FSb15tMH4PJcSbU780xTl9zUi7Zw.RAPdFTM7c33o6 wY0o3W_oYaxtPtTqA.YIudpeA.VY7615kdsUUeE6m01z0sBoLsMdbKFmRXxA ASK3qb9mdOxME0.Q1PT9Qos1EE352HUaj5zt.1YsiD3qVB2yi32hWKCqD60k u2uF_jkMqno8ThS0fNKlo0MMrWUxm2Zhyha3VcVPmMc_7gdhX_Rydhe3PV7J mDnuBBMW35__9RvObJv6RJMCu39i6TF27a1Fawao2hD.pD_5TGPIFYafb8Gd _otD6VdC3ZBTeiCTvdR5mwt07hf243ElfSj_OtcHWmqrlU51CeY2EmAJycSN 6chhgL7rATlUInTmtvttadtF6VcLfSgkqHNoTBCwrDMkns5WlTvNUtR81oV4 66rjDIerPHByr8yT0eeAZE7CR8FKCrRuaUn_88.d4wZ5XslsdqjVIujAjBrQ DSMJVzuPj2ZtI X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ-- Received: from [10.0.1.4] (david_jencks@76.76.148.215 with plain) by smtp104.prem.mail.sp1.yahoo.com with SMTP; 26 Sep 2011 17:43:55 -0700 PDT From: David Jencks Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-17--525382311 Subject: Re: [DISCUSS] What are the most wanted features in final Geronimo 3.0 Date: Mon, 26 Sep 2011 17:43:53 -0700 In-Reply-To: To: dev@geronimo.apache.org References: Message-Id: X-Mailer: Apple Mail (2.1084) --Apple-Mail-17--525382311 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Sep 24, 2011, at 6:45 AM, Ivan wrote: > Hi, devs,=20 > Think that most of work of Geronimo 3.0 beta is done, and we will = not introduce some major changes, and seems that the only dependencies = are some other third party components. Now we could go ahead to have an = overview for Geronimo 3.0. and what features are most important in the = 3.0. > The items below is somewhat I would like to see, and appreciate = any comment. > a. Server runtime side : > a1. Now, we have issues while the same packages with different = versions exported, and in the deployment process, currently, a system = property is introduced to identify whether the fixed import version = scope is used, e.g. org.apache.***;version=3D[1.0,1.0] or = org.apache.***;version=3D1.0. In the new OSGi 4.3, the new resolver hook = API should be helpful for this. > a2. Remove the dynamic import *, now we use it in two places, = one is in the temp bundle in the deployment process, and another is car = package. > a3. Use application scoped configuration, I have mentioned it = in the past, I really do not like so many system properties in the = server codes, there is a JIRA GERONIMO-5813 for this. With this, server = will have fine-grained configurations per module. > a4. Reconsider EAR support, I am thinking that we might = still divide the EAR to n+1 bundles, although it is not required by the = Java EE spec. In some current application programming, it seems to be a = default mind. e.g. Recently, I just fixed an issue in MyFaces = integration, > as it uses the classloader as the key for each web = application. > b. Web Service: > b1. Improve Axis2 integration, now some parsing work is done = each time while starting up the application, e.g. build the endpoint = structure. It is better to have some metadata there, and actually, we = have done this on web application, JSF integration etc. > b2. Provide a portlet for the web service, e.g. show web = service information per application, generate client artifacts on the = fly etc. > b3. Better support for ws-security, I remembered that we = have done some initial integration for this in the past. > c. Enable Jetty Assembly, most work should be on CXF side, I = guess. > d. Cluster/Farm related features > e. ActiveMQ integration improvement, we should provide a simple = way for the end users to configure the broker, and also add/remove = brokers. > f. WInk integration improvement, e.g. GERONIMO-6122 > g. Take advantage of more OSGi 4.3 new features, I knew that we = might use the new wiring API for calculating wired bundles. > ... > I knew that David is working on some OSGi-friendly changes, and = introduce the Karaf features, some of the ideas above are required to = consider those changes, anyway, just some ideas, thoughts ? :-) > --=20 What I would like for 3.0 is to get the work I've been doing to make the = gbean framework more compatible with osgi into trunk and to use the tx = manager in my sandbox. As part of this I moved away from using xmlbeans = for geronimo plans. If we get this to work I'd like to make all the deployers into = extenders: I already did this in the sandbox tm. Generally I think the = way to do this is to build an info tree (like we do for web and ejb = apps) and set up the application from it. For "precompiled" apps we can = write these into the bundle, for plain bundles we can write these into = the data area, and for new bundles just generate them. Again the = sandbox tm does this. I think this would provide an architecturally satisfactory base on which = to add functionality and also gradually replace gbeans with other styles = of osgi services. However I think this will be a lot of work and think if we all work on = it we might get it done by the end of the year. thanks david jencks > Ivan --Apple-Mail-17--525382311 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi, = devs, 
    Think that most of work of Geronimo 3.0 = beta is done, and we will not introduce some major changes, and seems = that the only dependencies are some other third party components. Now we = could go ahead to have an overview for Geronimo 3.0. and what features = are most important in the 3.0.
    The items below is somewhat I would like to see, and = appreciate any comment.
    a. Server runtime side = :
        a1. Now, we have issues while = the same packages with different versions exported, and in the = deployment process, currently, a system property is introduced to = identify whether the fixed import version scope is used, e.g. = org.apache.***;version=3D[1.0,1.0] or org.apache.***;version=3D1.0. In = the new OSGi 4.3, the new resolver hook API should be helpful for = this.
        a2. Remove the dynamic import *, now we = use it in two places, one is in the temp bundle in the deployment = process, and another is car package.
      =   a3. Use application scoped configuration, I have mentioned it in = the past, I really do not like so many system properties in the server = codes, there is a JIRA GERONIMO-5813 for this. With this, server = will have fine-grained configurations per module.
          a4. =  Reconsider EAR support, I am thinking that we might still divide = the EAR to n+1 bundles, although it is not required by the Java EE spec. = In some current application programming, it seems to be a default mind. = e.g. Recently, I just fixed an issue in MyFaces = integration,
            =      as it uses the classloader as the key for each web = application.
      b. Web = Service:
         b1. Improve = Axis2 integration, now some parsing work is done each time while = starting up the application, e.g. build the endpoint structure. It is = better to have some metadata there, and actually, we have done this on = web application, JSF integration etc.
         b2. Provide a = portlet for the web service,  e.g. show web service information per application, = generate client artifacts on the fly = etc.
         b3. Better = support  for ws-security, I remembered that we have done some = initial integration for this in the past.
     c. Enable Jetty Assembly, = most work should be on CXF side, I guess.
     d. Cluster/Farm related = features
     e. ActiveMQ integration = improvement, we should provide a simple way for the end users to = configure the broker, and also add/remove brokers.
      f. WInk integration = improvement,  e.g. GERONIMO-6122
    g. Take advantage of more OSGi 4.3 new features, I = knew that we might use the new wiring API for calculating wired = bundles.
    ...
    I knew that = David is working on some OSGi-friendly changes, and introduce the Karaf = features, some of the ideas above are required to consider those = changes, anyway, just some ideas, thoughts ? :-)
--

What I = would like for 3.0 is to get the work I've been doing to make the gbean = framework more compatible with osgi into trunk and to use the tx manager = in my sandbox.  As part of this I moved away from using xmlbeans = for geronimo plans.

If we get this to work I'd = like to make all the deployers into extenders: I already did this in the = sandbox tm.  Generally I think the way to do this is to build an = info tree (like we do for web and ejb apps) and set up the application = from it.  For "precompiled" apps we can write these into the = bundle, for plain bundles we can write these into the data area, and for = new bundles just generate them.  Again the sandbox tm does = this.

I think this would provide an = architecturally satisfactory base on which to add functionality and also = gradually replace gbeans with other styles of osgi = services.

However I think this will be a lot of = work and think if we all work on it we might get it done by the end of = the year.

thanks
david = jencks


Ivan

= --Apple-Mail-17--525382311--