bug #7910: TeamOrPersonField: readonly exception on bindig data - EDIT - EDIT Project Management

Actions

Copy link

bug #7910

closed

TeamOrPersonField: readonly exception on bindig data

Added by Andreas Kohlbecker over 5 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

Highest

Assignee:

Andreas Kohlbecker

Category:

cdm-vaadin

Target version:

Release 5.5

Start date:

Due date:

% Done:

100%

Estimated time:

Severity:

normal

Found in Version:

Tags:

phycobank

Description

Caused by: com.vaadin.data.Buffered$SourceException
    at com.vaadin.ui.AbstractField.setPropertyDataSource(AbstractField.java:664)
    at com.vaadin.data.fieldgroup.FieldGroup.bind(FieldGroup.java:273)
    at com.vaadin.data.fieldgroup.BeanFieldGroup.bind(BeanFieldGroup.java:155)
    at com.vaadin.data.fieldgroup.FieldGroup.bindFields(FieldGroup.java:113)
    at com.vaadin.data.fieldgroup.FieldGroup.setItemDataSource(FieldGroup.java:103)
    at com.vaadin.data.fieldgroup.BeanFieldGroup.setItemDataSource(BeanFieldGroup.java:126)
    at eu.etaxonomy.cdm.vaadin.component.common.TeamOrPersonField.setInternalValue(TeamOrPersonField.java:205)
    at eu.etaxonomy.cdm.vaadin.component.common.TeamOrPersonField.setInternalValue(TeamOrPersonField.java:1)
    at com.vaadin.ui.AbstractField.setValue(AbstractField.java:526)
    at eu.etaxonomy.cdm.vaadin.component.common.TeamOrPersonField.setValue(TeamOrPersonField.java:387)
    at eu.etaxonomy.cdm.vaadin.view.name.TaxonNamePopupEditor.updateAuthorshipFieldData(TaxonNamePopupEditor.java:658)
    at eu.etaxonomy.cdm.vaadin.view.name.TaxonNamePopupEditor.updateAuthorshipFields(TaxonNamePopupEditor.java:588)
    at eu.etaxonomy.cdm.vaadin.view.name.TaxonNamePopupEditor.lambda$13(TaxonNamePopupEditor.java:681)
    at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
    ... 98 more
Caused by: com.vaadin.data.Property$ReadOnlyException
    at com.vaadin.ui.AbstractField.setValue(AbstractField.java:493)
    at com.vaadin.ui.AbstractField.setValue(AbstractField.java:468)
    at com.vaadin.ui.AbstractField.setValue(AbstractField.java:453)
    at eu.etaxonomy.cdm.vaadin.component.common.PersonField.setValue(PersonField.java:280)
    at eu.etaxonomy.cdm.vaadin.component.common.PersonField.setValue(PersonField.java:1)
    at eu.etaxonomy.vaadin.component.ToManyRelatedEntitiesListSelect.createFieldsForData(ToManyRelatedEntitiesListSelect.java:270)
    at eu.etaxonomy.vaadin.component.ToManyRelatedEntitiesListSelect.setInternalValue(ToManyRelatedEntitiesListSelect.java:246)
    at eu.etaxonomy.vaadin.component.ToManyRelatedEntitiesListSelect.setInternalValue(ToManyRelatedEntitiesListSelect.java:1)
    at com.vaadin.ui.AbstractField.setPropertyDataSource(AbstractField.java:657)
    ... 114 more

Related issues

Actions

Copy link

Updated by Andreas Kohlbecker over 5 years ago

Status changed from New to In Progress

The root of this problem is the Team class in which the setter for members is protected. This causes the PropertyDataSourcebeing readonly due to the missing setter for this bean property.

The TermOrPersonField already has a hacky workaround to allow modifying the team members anyway:

fieldGroup.setItemDataSource(new BeanItem<Team>((Team)newValue)); // <<NEW PROBLEM
boolean readonlyState = personsListEditor.isReadOnly();
fieldGroup.bind(personsListEditor, "teamMembers"); // here personField is set readonly since setTeamMembers does not exist
personsListEditor.setReadOnly(readonlyState); // fixing the readonly state