[ http://jira.jboss.com/jira/browse/JBPORTAL-1637?page=comments#action_1237... ] Boleslaw Dawidowicz commented on JBPORTAL-1637: ----------------------------------------------- also you should check PropertyInfo.getAccessMode() to check for read-only props. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1637?page=comments#action_1237... ] Thomas Heute commented on JBPORTAL-1637: ---------------------------------------- "Mandatory" and "type" are already there :) Nice. Why is it used today ? Does the user portlet check this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1637?page=comments#action_1237... ] Boleslaw Dawidowicz commented on JBPORTAL-1637: ----------------------------------------------- most of them are not used right now (it was actually added having dynamic jsp page creation in mind ;)). I have also other ones on plate for 2.8 related to profile http://jira.jboss.com/jira/browse/JBPORTAL-1493 http://jira.jboss.com/jira/browse/JBPORTAL-1494 I'm open for all the suggestions as I don't know all the use cases from UI point of view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1637?page=comments#action_1237... ] Boleslaw Dawidowicz commented on JBPORTAL-1637: ----------------------------------------------- If you want to have separate config for UserPortlet I should probably move some of those options to your file because it'll be doubled. But when I think about it.... 2 separate files with similar content - a list of properties but with different parameters... looks like a config nightmare to me :) So to add remove a property you need to put that info into two files. Maybe it would be better to workout common list of meta-data describing user property and extend current property-info.xml. The nature of the API is that its easy to extend and difficult to remove :) The question is: What does it buy us to have separate configuration for UserPortlet for stuff that can be gathered from existing metadata. There will be changes in identity in 2.8 but for this part it should be rather evolution than revolution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1637?page=comments#action_1237... ] Boleslaw Dawidowicz commented on JBPORTAL-1637: ----------------------------------------------- ok.... <should_property_name_blink_when_mouse_is_over> won't be the best tag to place in profile-config.xml indeed :) If you think that some of the current metadata should be rather placed in UI configuration, or you have something in mind that should be add to identity metadata let me know. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira