Hi Azeez, So in the runtime environments scenario, we have some duplication between runtime vs the plugins. But the argument in here is that a user should be able to use/sxpose the runtime only and get their job done. For eg: user has a jax-rs application. So he will expose the cxf runtime env. to the app. But he won't expose carbon. So in this case we need to have all cxf dependencies too within the cxf runtime env.
thanks, On Fri, Jun 21, 2013 at 7:12 AM, Afkham Azeez <[email protected]> wrote: > I think the size can be reduced a lot by reviewing & removing duplicated > jars & unnecessary stuff, before we start thinking of P2 > > Azeez > > > On Thu, Jun 20, 2013 at 5:43 PM, Sagara Gunathunga <[email protected]>wrote: > >> >> Size of the AS distribution becoming very large with last few releases. >> AS 4.1.2 is about 160 MB and AS 5.1.0 is around 200 MB my current >> understanding is AS size will become around 230/240 MB in AS 5.2.0 release >> with JSF, JPA and JTA support, basically once we support for J2EE-WP spec >> AS end up with extra ~100 MB. >> >> WSO2 product/features can be installed to AS through P2 repo hence it's >> not an issue here. But still it's not clear whether we could use any P2 >> based solution to add Classlaoder Environments (CLE) to the basic AS >> distribution. >> >> For AS 5.2.0 we have following CLEs addition to basic Carbon and Tomcat >> CLEs. >> >> 1. CXF ( ~20 to ~25 MB) >> 2. J2EE ( ~ 30 MB) >> >> >> It's not possible to use P2 mechanism as it is to install CLEs because >> those are not instilled to OSGi runtime instead they stay out side the OSGi >> runtime. Following are the steps we need to perform to add a CLE to AS. >> >> 1. Modify and add an entry to the "webapp-classloading-environments.xml" >> file located on "repository/conf/tomcat" directory. >> >> 2. Copy a directory with set of Jar files into the "lib/runtimes" >> directory. >> >> 3. Copy some samples to the "samples" directory (Optional). >> >> >> Above tasks can be easily done with small Ant script but it would be much >> better to use P2 as it's the platform level mechanism to add new features. >> Any idea how we could do this using P2 ? >> >> Thanks ! >> >> -- >> Sagara Gunathunga >> >> Senior Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
