The reason for introducing this component mainly is for allowing tenants to manage their Axis repositories. If there are shared libraries, they can place it in the relevant lib directories and 'restart' their AxisConfigurations.
Azeez On Fri, Oct 1, 2010 at 10:04 AM, Shariq <[email protected]> wrote: > Hi, > > At present, I am working on developing a Carbon Component to manage the > Axis2 Repository. > The purpose of this component is to provide the capability to add common > jars, libs etc. to the /lib directory via the Management Console. > > Currently I am using following names and package structure. > > Component name - Axis2 Repository Management > Top level package - axis2-repo-mgt > BE hierarchy - org.wso2.carbon.repomanager > FE hierarchy - org.wso2.carbon.repomanager.ui > Service - Axis2RepoManager > > If any modification are required to any names or package structure please > let me know. > > Thank you, > Shariq. > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Afkham Azeez* Senior Software Architect & Senior Manager; 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*
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
