Have we reviewed this? shall I schedule?

--Srinath


On Mon, May 27, 2013 at 5:42 PM, Amila Suriarachchi <[email protected]> wrote:

>
>
>
> On Mon, May 27, 2013 at 5:30 PM, Prabath Siriwardena <[email protected]>wrote:
>
>>
>>
>> On Mon, May 27, 2013 at 5:13 PM, Amila Suriarachchi <[email protected]>wrote:
>>
>>>
>>>
>>>
>>> On Mon, May 27, 2013 at 5:01 PM, Prabath Siriwardena 
>>> <[email protected]>wrote:
>>>
>>>>
>>>>
>>>> On Mon, May 27, 2013 at 4:04 PM, Amila Suriarachchi <[email protected]>wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, May 27, 2013 at 3:06 PM, Prabath Siriwardena <[email protected]
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 24, 2013 at 9:51 PM, Amila Suriarachchi 
>>>>>> <[email protected]>wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>    - Saving data inserted via UI, at finish -  This has few
>>>>>>>>    options. Please advice on best to use
>>>>>>>>    - Update the RealmService with new configuration and then write
>>>>>>>>       the updated Realmconfiguration into user-mgt.xml (This newly 
>>>>>>>> created file
>>>>>>>>       will trigger the Axis2 deployer as a new file addition, which is 
>>>>>>>> not needed
>>>>>>>>       )
>>>>>>>>       - Write the updated details into user-mgt.xml. Even if only
>>>>>>>>       one UserStoreManager is edited, whole user-mgt.xml has to be 
>>>>>>>> read in, place
>>>>>>>>       new one in relevant order and update other's order accordingly.
>>>>>>>>
>>>>>>>>
>>>>>>> Idea is to create a separate file per user store. you can save this
>>>>>>> file with the userstore name. Then update only that file.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> I don't think we need to keep files per user store. We can persist
>>>>>> the changes to the user-mgt.xml it self and keep different user-mgt.xml
>>>>>> files per tenant..
>>>>>>
>>>>>
>>>>> As we discussed last time user-mgt.xml is used to represent realm
>>>>> which consists of user store, authorization manager, clam manager etc ...
>>>>> Since authorization manager, claim manger stuff are already multi tenanted
>>>>> we don't need to have a user-mgt.xml per tenant.
>>>>>
>>>>> Here the requirement is to let users to add their user stores to the
>>>>> system. So adding stores as separate xml files simplify the design. These
>>>>> user stored does not need to support MT since it is specific to a tenant.
>>>>>
>>>>
>>>> I think that approach would be more scattered - to have multiple files
>>>> by user store..
>>>>
>>>
>>> This is the approach we follow for proxy services, cep buckets etc...
>>> For an example earlier we had only synapse.xml and cep-config.xml to define
>>> all. But now have separate ones.
>>>
>>> Another advantage is we need to update only one store. For an example if
>>> every one edits the same user-mgt.xml then when a user adds one user store,
>>> I think all other stores need to update as well. Since for deployment
>>> engine it is an update of the file.
>>>
>>
>>
>> My argument is - this is different from other service artifacts.. These
>> operations do not happen frequently - so - I guess having a single file
>> would make things simple...
>>
>
> IMHO the main point is, it is not the correct design. Please see this
> reply.
>
>
> As we discussed last time user-mgt.xml is used to represent realm which
> consists of user store, authorization manager, clam manager etc ... Since
> authorization manager, claim manger stuff are already multi tenanted we
> don't need to have a user-mgt.xml per tenant.
>
> Anyway lets do a code review after implementing this either way.
>
> thanks,
> Amila.
>
>
>
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>>>
>>> thanks,
>>> Amila.
>>>
>>>
>>>>
>>>> Thanks & regards,
>>>> -Prabath
>>>>
>>>>
>>>>>
>>>>> thanks,
>>>>> Amila.
>>>>>
>>>>>
>>>>>>  Thanks & regards,
>>>>>> -Prabath
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> thanks,
>>>>>>> Amila.
>>>>>>>
>>>>>>>>
>>>>>>>>    -
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Pushpalanka Jayawardhana
>>>>>>>>
>>>>>>>> Software Engineer
>>>>>>>>
>>>>>>>> WSO2 Lanka (pvt) Ltd
>>>>>>>> [image: 
>>>>>>>> Facebook]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.facebook.com%2Fpushpalanka>
>>>>>>>>  [image:
>>>>>>>> Twitter]<http://s.wisestamp.com/links?url=http%3A%2F%2Ftwitter.com%2FPushpalanka>
>>>>>>>>  [image:
>>>>>>>> LinkedIn]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.linkedin.com%2Fprofile%2Fview%3Fid%3D75175642%26trk%3Dtab_pro>
>>>>>>>>  [image:
>>>>>>>> Blogger]<http://s.wisestamp.com/links?url=http%3A%2F%2Fpushpalankajaya.blogspot.com%2F>
>>>>>>>>  [image:
>>>>>>>> SlideShare]<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.slideshare.net%2FPushpalanka>
>>>>>>>> Mobile: +94779716248
>>>>>>>> <http://s.wisestamp.com/links?url=http%3A%2F%2Fr1.wisestamp.com%2Fr%2Flanding%3Fu%3Dc984892c0c4ca423%26v%3D3.13.2%26t%3D1361257731639%26promo%3D10%26dest%3Dhttp%253A%252F%252Fwww.wisestamp.com%252Femail-install%253Futm_source%253Dextension%2526utm_medium%253Demail%2526utm_campaign%253Dpromo_10>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Architecture mailing list
>>>>>>>> [email protected]
>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Amila Suriarachchi*
>>>>>>>
>>>>>>> Software Architect
>>>>>>> WSO2 Inc. ; http://wso2.com
>>>>>>> lean . enterprise . middleware
>>>>>>>
>>>>>>> phone : +94 71 3082805
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Architecture mailing list
>>>>>>> [email protected]
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks & Regards,
>>>>>> Prabath
>>>>>>
>>>>>> Mobile : +94 71 809 6732
>>>>>>
>>>>>> http://blog.facilelogin.com
>>>>>> http://RampartFAQ.com
>>>>>>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Amila Suriarachchi*
>>>>>
>>>>> Software Architect
>>>>> WSO2 Inc. ; http://wso2.com
>>>>> lean . enterprise . middleware
>>>>>
>>>>> phone : +94 71 3082805
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>> Prabath
>>>>
>>>> Mobile : +94 71 809 6732
>>>>
>>>> http://blog.facilelogin.com
>>>> http://RampartFAQ.com
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> *Amila Suriarachchi*
>>>
>>> Software Architect
>>> WSO2 Inc. ; http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> phone : +94 71 3082805
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
============================
Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to