Hi all, Currently RXTs do not support password fields and I'm working on implementing this.
This implementation has a UI aspect which masks the contents of password fields when rendered in web browser, and secured store aspect where contents of password field should be encrypted when storing, and should be decrypted when retrieving. Considering the implementation of UI aspect of password field it can be implemented in following ways, 1. Create a new "PasswordField" class similar to "TextField", in "org.wso2.carbon.governance.generic.ui.common.dataobjects" 2. Add an attribute to "TextField" class, in "org.wso2.carbon.governance.generic.ui.common.dataobjects" to determine whether this text field should be viewed as a normal text field or as a password field. IMO as password field differ only by masking the content in the text field, it is suitable to go with the 2nd solution. What other factors should be concerned when implementing the UI aspect of password field for RXTs? Thank you, SameeraK -- Sameera Kannangara, Software Engineer, WSO2 Inc.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
