Identifying minimal 3rd party component set for each product.

[Pradeep Fernando <pr...@gmail.com>]

Hi Devs,

Right now Apache Stratos products packs number of 3 rd party features
(org.wso2.carbon... features) during product installation. These features
are coarse grained and tailored for  the respective organizations' use
case. We should identify the minimal 3 rd party dependency set and include
only those..

proposed approach:

- create a one monolithic feature that includes all the 3 rd partly
components...
- eliminate unwanted components (bundle/jar level) one by one from that
feature.

wdyt ?

--Pradeep

Re: Identifying minimal 3rd party component set for each product.

[Pradeep Fernando <pr...@gmail.com>]

Hi Paul,

Yes sure will get the help from bundle authors. However, our main concern
is features at this moment..
Feature include a coarse grained functionality and existing third party
features do not meet our exact requirement.. Hence thought of creating our
own feature for third party bundles and re-factor it to be minimal.


for an example,

right now ELB installs,

mediation-feature, which requires another feature A and feature B.

however stratos requires only synapse.core bundle found inside mediation
feature. Hence thought of creating a stratos feature called,

org.apache.stratos.3rdpary.bundles.feature and include only the necessary
bundles in to that.
The effort is targeted to eliminate the unwanted bundle installations... I
agree with your suggestion. But that would be a next step IMHO...

--Pradeep







On Mon, Sep 16, 2013 at 12:53 PM, Paul Fremantle <pa...@wso2.com> wrote:

> Pradeep
>
> I agree this is a good approach. Can you follow up with a #3: identify any
> recommendations about the packaging of the existing 3rd party bundles. I'm
> sure the originators of the bundles would be happy to refactor them to be
> more efficient if that was a recommendation from Apache.
>
> Paul
>
>
> On 16 September 2013 08:04, Pradeep Fernando <pr...@gmail.com> wrote:
>
>> Hi Devs,
>>
>> Right now Apache Stratos products packs number of 3 rd party features
>> (org.wso2.carbon... features) during product installation. These features
>> are coarse grained and tailored for  the respective organizations' use
>> case. We should identify the minimal 3 rd party dependency set and include
>> only those..
>>
>> proposed approach:
>>
>> - create a one monolithic feature that includes all the 3 rd partly
>> components...
>> - eliminate unwanted components (bundle/jar level) one by one from that
>> feature.
>>
>> wdyt ?
>>
>> --Pradeep
>>
>>
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, Apache Member
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> paul@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
Pradeep Fernando.
http://pradeepfernando.blogspot.com/

Re: Identifying minimal 3rd party component set for each product.

[Paul Fremantle <pa...@wso2.com>]

Pradeep

I agree this is a good approach. Can you follow up with a #3: identify any
recommendations about the packaging of the existing 3rd party bundles. I'm
sure the originators of the bundles would be happy to refactor them to be
more efficient if that was a recommendation from Apache.

Paul


On 16 September 2013 08:04, Pradeep Fernando <pr...@gmail.com> wrote:

> Hi Devs,
>
> Right now Apache Stratos products packs number of 3 rd party features
> (org.wso2.carbon... features) during product installation. These features
> are coarse grained and tailored for  the respective organizations' use
> case. We should identify the minimal 3 rd party dependency set and include
> only those..
>
> proposed approach:
>
> - create a one monolithic feature that includes all the 3 rd partly
> components...
> - eliminate unwanted components (bundle/jar level) one by one from that
> feature.
>
> wdyt ?
>
> --Pradeep
>
>
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, Apache Member

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
paul@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.