[
https://issues.apache.org/jira/browse/TAP5-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769799#action_12769799
]
Igor Drobiazko commented on TAP5-907:
-------------------------------------
The described behavior is expected. You can't reorder a property which doesn't
exist. If there is no setter method for a property the edit model is not aware
of this property. The problem is the inconsistency of your edit and display
models. These model have different sets of properties but you put a set union
into the @ReorderProperties annotation. You should put an intersection of
common properties instead or reorder the properties in template.
I think we can close this issue.
> BeanModelImpl.reorder
> ---------------------
>
> Key: TAP5-907
> URL: https://issues.apache.org/jira/browse/TAP5-907
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Alex Lumpov
>
> I have MyBean with rw and read-only properties.
> MyBean have @ReorderProperties annotation (it include read-only properties).
> When BeanModelSourceImpl creates display model everything is fine.
> When BeanModelSourceImpl creates edit model I saw exception:
> org.apache.tapestry5.internal.beaneditor.BeanModelImpl.get(BeanModelImpl.java:152)
> org.apache.tapestry5.internal.beaneditor.BeanModelImpl.reorder(BeanModelImpl.java:213)
>
> because BeanModelImpl.reorder try to get property that not exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
