And, IMO, the following are not needed. 1. cipher-text.properties 2. embedded-ldap.xml (can be merged into user-mgt.xml right?) 3. node/* (these are outdated and no longer needed, AFAIU). 4. secret-conf.properties
The secure-vault documentation should include how to create these files if needed, as they are not mandatory. And, most importantly, we need to s/README/README.txt, or you can't open it in Windows properly. Also, may be we need to use the DOS line-encoding for these files. Can this be done by setting svn:eol-style? And, I have a small question. Is the file name wrapper.conf correct? I'm talking about the extension, is conf correct? Thanks, Senaka. On Tue, Mar 8, 2011 at 10:22 AM, Afkham Azeez <[email protected]> wrote: > Please feel free to remove these ASAP. If they are not used, they should > not cause any issues. > > Azeez > > > On Tue, Mar 8, 2011 at 10:20 AM, Thilina Buddhika <[email protected]>wrote: > >> There is an entry in carbon.xml for key store directory which is no longer >> in use. We can remove this entry from the carbon.xml. >> >> >> <KeyStoresDir>${carbon.home}/repository/resources/security</KeyStoresDir> >> >> >> Also in identity.xml (this is specific to Identity Server), following >> configuration is not used. >> >> <UserPersonalCeritificateStore> >> >> >> <Location>${carbon.home}/repository/resources/security/wso2is-user-certs.jks</Location> >> <!-- Keystore type (JKS/PKCS12 etc.)--> >> <Type>JKS</Type> >> <!-- Keystore password--> >> <Password>wso2is</Password> >> <!-- Private Key password--> >> <KeyPassword>wso2is</KeyPassword> >> </UserPersonalCeritificateStore> >> >> So as part of this process, we are planning to get rid of the above >> mentioned entries. >> >> Thanks, >> Thilina >> >> >> On Tue, Mar 8, 2011 at 7:30 AM, Afkham Azeez <[email protected]> wrote: >> >>> Folks, >>> We have to $subject. This is of utmost importance since this is one of >>> the things that the users look at. I can remember sometime back some users >>> complaining that we have too many XML files. In our case, at least we could >>> have some documentation in the file itself which explains its purpose. Also, >>> people have added all sorts of stuff to carbon.xml. >>> >>> Can we please have a look at this ASAP? >>> >>> Can the people who added these files add header comments & README file >>> comments please? In future, please consult the others before adding new >>> config file elements, or new config files. >>> >>> Thanks >>> Azeez >>> >>> -- >>> *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] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Thilina Buddhika >> Senior Software Engineer >> >> WSO2 Inc. ; http://wso2.com >> lean . enterprise . middleware >> >> phone : +94 77 44 88 727 >> blog : http://blog.thilinamb.com >> > > > > -- > *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] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
