I am not saying this is a bug exactly. If this is expected behavior then we
should document it IMO. WDYT?

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Wed, Mar 4, 2015 at 2:16 PM, Susinda Perera <[email protected]> wrote:

> It seems a bug, since it is already configured in a file we can read the
> config on server startup. Dont see a use case of again save the same on
> local registry.
>
> On Wed, Mar 4, 2015 at 2:05 PM, Dimuthu Leelarathne <[email protected]>
> wrote:
>
>> Hi,
>>
>> AFAIK, most people know this.
>>
>> Changing mounts is not something we do everyday. We need to clearly
>> specify the mounting process.
>>
>> thanks,
>> dimuthu
>>
>>
>> On Wed, Mar 4, 2015 at 1:57 PM, Danushka Fernando <[email protected]>
>> wrote:
>>
>>> Hi all
>>> Currently if we start a server with some registry mounting configuration
>>> then it will save those to the local registry. And at some point if we
>>> change those configuration then this local registry doesn't get reflected.
>>>
>>> So the mounting configuration changes will not be effective until we
>>> clean the local database.
>>>
>>> Is this a bug or is it how it is designed? If this is the expected
>>> behavior then we need to document this somewhere.
>>> WDYT?
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729
>>>
>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: [email protected]
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to