Have you already started working on this? I would prefer a ciphertool.properties or ciphertool.conf file, rather than System properties. If the file is not present, fallback to carbon.xml. However, to make this truly independent from Carbon, you should not take any dependency on Carbon kernel or components.
On Thu, Nov 27, 2014 at 11:13 PM, Nirmal Fernando <[email protected]> wrote: > Hi All, > > Currently, our Cipher tool implementation is dependent upon Carbon runtime > specific configuration files such as carbon.xml [1]. > > The idea is to, let you configure and run Cipher tool by simply setting > System properties, so that you can utilize the tool to encrypt passwords > even without having a Carbon runtime available. > > Of course, the current behavior will also be preserved, that is; if the > System properties are not present, the required values will be read from > the Carbon runtime specific configurations. > > Please share your thoughts. > > [1] > https://github.com/wso2/commons/blob/master/ciphertool/src/main/java/org/wso2/ciphertool/CipherTool.java#L290 > > -- > > Thanks & regards, > Nirmal > > Senior Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > -- *Afkham Azeez* Director of Architecture; 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 3320919blog: **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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
