[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9947. -------------------------------- Resolution: Done validation status has been added =] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9947: ------------------------------------ Attachment: validate-runtime.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9947 at 10/19/11 3:48 PM: ------------------------------------------------------------------- attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" combo - "available runtimes" - "selected runtime" To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values (and not in widgets/beans). The MultiValidator tracks behind the scene what observables are accessed and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the validation value change. was (Author: adietish): attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" combo - "available runtimes" - "selected runtime" To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values. The MultiValidator tracks behind the scene what observables you access and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the validation value change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9947 at 10/19/11 3:56 PM: ------------------------------------------------------------------- attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" combo - "available runtimes" - "selected runtime" !validate-runtime.png! To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values (and not in widgets/beans). The MultiValidator tracks behind the scene what observables are accessed and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the validation value change. was (Author: adietish): attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" combo - "available runtimes" - "selected runtime" To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values (and not in widgets/beans). The MultiValidator tracks behind the scene what observables are accessed and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the validation value change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9947 at 10/20/11 2:37 AM: ------------------------------------------------------------------- attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" checkbox - "available runtimes" items in the combo - "selected runtime" selected combo item !validate-runtime.png! To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values (and not in widgets/beans). The MultiValidator tracks behind the scene what observables are accessed and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the values, that participate in the validation, change. was (Author: adietish): attached a patch, need intense checking. Basically the problem here is that we validate on behalf of several properties: - "create adapter" combo - "available runtimes" - "selected runtime" !validate-runtime.png! To solve this with databinding we do not add validators to bindings. Validators in bindings are only able to validate single values (not composite properties). In databinding we add a MultiValidator to the DataBindingContext. The only tricky part is that you have to access all values, that take part in the the validation result, on behalf of observable values (and not in widgets/beans). The MultiValidator tracks behind the scene what observables are accessed and elaborates when he has to revalidate instead of returning a cached value. If your validator impl accesses the validation values in widgets (not observables), then the validator wont be called when the values, that participate in the validation, change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-9947. ------------------------------------- Resolution: Done I also cleaned the layout a bit so that all actual widgets get left aligned below each other. committed to TRUNK (Beta1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9947 at 10/20/11 5:50 PM: ------------------------------------------------------------------- I also cleaned the layout a bit so that all actual widgets get left aligned below each other (and centered vertically if displayed in 1 row). committed to TRUNK (Beta1) was (Author: adietish): I also cleaned the layout a bit so that all actual widgets get left aligned below each other (and centered horizontally if displayed in 1 row). committed to TRUNK (Beta1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9947?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9947. -------------------------------- I'm closing this JIRA as it is out of date. The behavior is different now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira