Hi all,

One of the re-factoring task we followed in previous milestones is to use
OSGI calls instead of service calls to avoid the performance hit.

Are we planing to use cloud-mgt without AppFactory deployments? If yes, you
can get rid of AppFactory dependencies. User management should be a part of
IS, so the user management jaggery app modules should come from IS not
within cloud-mgt itself. Then we can use them in AppFactory as well in
cloud setups. WDYT?

thank you.


On Thu, Jan 9, 2014 at 12:13 PM, Amila Maha Arachchi <[email protected]>wrote:

> Moving the discussion to dev list.
>
>
> On Thu, Jan 9, 2014 at 12:07 PM, Amani Soysa <[email protected]> wrote:
>
>> In current user-mgt implementation, there are serveral custom codes
>> written in appfactory code base. Therefore, if we extract user-mgt section
>> completely from app-mgt we might have to add appfactory dependancies to
>> cloud mgt (ie
>> org.wso2.carbon.appfactory.tenant.mgt,org.wso2.carbon.appfactory.common,org.wso2.carbon.appfactory.core).
>>
>> And also in the user-mgt code base, I've seen some backend calls are done
>> using service calls and some are OSGi calls. Since having service calls can
>> lead to multiple threads and performance issues shall I convert all service
>> calls in to OSGi calls and add above appfactory dependencies to the
>> cloudmgt?
>>
>> What is the most preferable way of doing this?
>>
>> --
>> Amani Soysa
>> Senior Software Engineer
>> Mobile: +94772325528
>> WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to