[Carbon-dev] Axis2 dependency in Carbon 3.0.0 needs to be updated for BAM

[Ruwan Linton]

Sameera Jayasoma wrote:
>
>
> On Fri, Apr 30, 2010 at 10:18 AM, Isuru Suriarachchi <isuru at wso2.com 
> <mailto:isuru at wso2.com>> wrote:
>
>
>
>     On Thu, Apr 29, 2010 at 4:57 PM, Sameera Jayasoma
>     <sameera at wso2.com <mailto:sameera at wso2.com>> wrote:
>
>
>
>         On Thu, Apr 29, 2010 at 3:20 PM, Dumindu Pallewela
>         <dumindu at wso2.com <mailto:dumindu at wso2.com>> wrote:
>
>             Hi All,
>
>             A patch I did to Axis2 local transport [1], which is in
>             Axis2 trunk doesn't seem to be in the carbon 3.0.0 branch.
>             We need that patch for BAM data services to work.
>
>             How can we get it in for the BAM release?
>
>
>         AFAIK, next BAM release will be based on Carbon 3.0.0 branch.
>         i.e. all the BAM related components/features should depend on
>         Carbon 3.0.0 bundles and features.
>
>         Carbon 3.0.0 features depend on Axis2 orbit bundle version
>         1.6.0-wso2v1. When you patch Axis2, you need to change the
>         orbit bundles version from 1.6.0-wso2v1 to 1.6.0-wso2v2. Now
>         there is an issue.
>
>         One solution would be release a new version of Carbon. Or else
>         we can patch Carbon 3.0.0 features(speciall
>         org.wso2.carbon.core.common.feature) using the mecanism of
>         feature patching.
>
>
>     >From our previous experiences of Carbon releases, we know that
>     even if it is a point release, there are at least three or four
>     changes in the dependent branches (Axis2, Synapse, Rampart etc.).
>     So I think doing  a point release depending 100% on the exact
>     Carbon version won't be a reality.
>
>     So if we are going to use feature patching to solve this problem
>     without doing a new carbon release, it will be great. But we have
>     to think about some important aspects..
>
>     * How are we going to maintain the patched code? Are we going to
>     create a new branch from the patched dependent project (Ex : Axis2)?
>
>
> IMV we need to branch Axis2 source and change the version to 
> 1.6-wso2v2. This results in changing the Axis2 orbit version to 
> 1.6.0.wso2v2.
May be I am a bit late on this :-(

By changing the axis2 version we are changing the carbon version... Why 
can't we use the patching approach for this, basically patch the axis2 
bundle shipped with the carbon-3.0.0.

How do we suppose to resolve an issue of the ESB-3.0.0 which needs 
changes to the axis2, does it require axis2 version to be upgraded to 
wso2v2? If not, why can't we do the same for the BAM and BPS releases????

Thanks,
Ruwan
>
> Sameera
>
>     * How are we going to make sure that those patches will be
>     included in the next point release as well?
>
>     Thanks,
>     ~Isuru
>      
>
>         I will send a more detailed explaination on the second approach.
>
>         Thanks
>         Sameera
>
>
>
>             Thanks,
>             Dumindu.
>
>             [1] https://issues.apache.org/jira/browse/AXIS2-4636
>
>             -- 
>             Dumindu Pallewela
>             WSO2 | "Lean . Enterprise . Middleware" | http://wso2.com
>
>             _______________________________________________
>             Carbon-dev mailing list
>             Carbon-dev at wso2.org <mailto:Carbon-dev at wso2.org>
>             https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
>         -- 
>         Sameera
>
>         -- 
>         Sameera Jayasoma
>         Senior Software Engineer
>         WSO2, Inc. (http://wso2.com)
>         email: sameera at wso2.com <mailto:sameera at wso2.com>
>         blog: http://tech.jayasoma.org
>
>         Lean . Enterprise . Middleware
>
>         _______________________________________________
>         Carbon-dev mailing list
>         Carbon-dev at wso2.org <mailto:Carbon-dev at wso2.org>
>         https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>     _______________________________________________
>     Carbon-dev mailing list
>     Carbon-dev at wso2.org <mailto:Carbon-dev at wso2.org>
>     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Sameera
>
> -- 
> Sameera Jayasoma
> Senior Software Engineer
> WSO2, Inc. (http://wso2.com)
> email: sameera at wso2.com <mailto:sameera at wso2.com>
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
> ------------------------------------------------------------------------
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
phone: +1 408 754 7388 ext 51789
email: ruwan at wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware