Revision d34cd38e
Added by Andreas Kohlbecker almost 6 years ago
| src/main/java/eu/etaxonomy/cdm/vaadin/component/common/TeamOrPersonField.java | ||
|---|---|---|
| 20 | 20 |
import com.vaadin.data.util.BeanItem; |
| 21 | 21 |
import com.vaadin.server.FontAwesome; |
| 22 | 22 |
import com.vaadin.server.UserError; |
| 23 |
import com.vaadin.shared.AbstractFieldState; |
|
| 23 | 24 |
import com.vaadin.ui.Button; |
| 24 | 25 |
import com.vaadin.ui.Component; |
| 25 | 26 |
import com.vaadin.ui.CssLayout; |
| ... | ... | |
| 387 | 388 |
@Override |
| 388 | 389 |
public void setValue(TeamOrPersonBase<?> newFieldValue) {
|
| 389 | 390 |
// ignore readonly states of the datasource |
| 390 |
setValue(newFieldValue, false, !super.isReadOnly()); |
|
| 391 |
setValue(newFieldValue, false, !hasSharedStateReadOnly()); |
|
| 392 |
} |
|
| 393 |
|
|
| 394 |
protected boolean hasSharedStateReadOnly(){
|
|
| 395 |
AbstractFieldState sharedState = getState(false); |
|
| 396 |
return sharedState.readOnly; |
|
| 391 | 397 |
} |
| 392 | 398 |
|
| 393 | 399 |
|
Also available in: Unified diff
finally solving the nasty readonly problem with TeamOrPersonBaseField on updating authorship information