Hi Shariq,

If you need to override values that should be done through a configuration
in the product level (e.g. bin.xml or something else). Even in IS we do
such a change to modify the default user-mgt.xml to use embedded ldap where
as other products use JDBC. We don't maintain a separate user-mgt.xml. This
is done through the pom.xml of modules/distribution inside IS product. By
having it at feature level it will cause problems to other products.


On Thu, Dec 5, 2013 at 2:07 PM, Shariq Muhammed <[email protected]> wrote:

> Hi Johann,
>
> Yeah this is a common problem in the platform, where some features as well
> as products maintain certain config files and to override the default once.
> There are many config files like registr.xml that are maintained locally
> within products/ as well. In identity.xml case here I think we can use an
> external, but if we want to override the default config file then we have
> to maintain a local copy. Since we are moving to git with C5, again we
> might have to revisit our options ...
>
>
>
> On Thu, Dec 5, 2013 at 1:32 AM, Johann Nallathamby <[email protected]>wrote:
>
>> Hi,
>>
>> This is a common problem in our platform.
>>
>> Ideally one kind of file should not be installed by multiple features. In
>> case it is unavoidable we should use svn externals to reference a file from
>> another location.
>>
>> E.g. Identity.xml file is being installed by stratos.common.server
>> feature. For starters I think an identity service specific config file
>> should not be installed by stratos. Even if it should we need to have an
>> svn external pointing it to identity.core.server feature. Because otherwise
>> since Identity Server installs both of these features it ends up having an
>> out-dated file from stratos.common.server feature.
>>
>> This is the same story with API Manager. It maintains a separate
>> identity.xml at the product level which leads to unwanted work.
>>
>> I fixed the stratos common feature by adding an svn external to
>> stratos.common.server-2.2.0 feature sometime back. But somehow in 2.2.1
>> version the file has been added back again. Once I am able to commit to
>> branch I will fix this again. Please see if this can removed completely.
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Senior Software Engineer
>> Integration Technologies Team
>>  WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+94777776950*
>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>
>
>
>
> --
> Thanks,
> M. S. M. Shariq.
> Senior Software Engineer
> Phone: +94 777 202 225
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Software Engineer
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+94777776950*
Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to