Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

2015-12-14 Thread Vangel V. Ajanovski
First of all, I have made a mistake in the subject - it was supposed to be 5.4-rc-1 On 14.12.2015 09:18, Chris Poulsen wrote: show. (If you are not using include, a number of things can go wrong like: the Degree class may evolved, the hibernate stuff may have added extra runtime properties

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

2015-12-14 Thread Chris Poulsen
I don't know what you mean by having tried many library combinations. But Tapestry related libs should all be the same version and without duplicates in your runtime. The error you are getting happens because the BeanModel for your grid already contains a property called "delete". So if you

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

2015-12-14 Thread Vangel V. Ajanovski
On 14.12.2015 12:50, Chris Poulsen wrote: The error you are getting happens because the BeanModel for your grid already contains a property called "delete". If I replace add="delete" with add="deleteHVUHDVIUDHVS" I will get a message that the Model already contains "deleteHVUHDVIUDHVS"

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

2015-12-14 Thread Vangel V. Ajanovski
On 14.12.2015 12:48, Thiago H de Paula Figueiredo wrote: Have you tried to @Inject BeanModelSource and call beanModelSource.createDisplayModel(yourClass.class, messages) and see what are the properties (PropertyModel instances) it detects? So in the tml I know have a random property name:

Re: 5.4-rc-1 - problem when *add* a column to a *grid*, but it is working OK in 5.4-beta-26

2015-12-14 Thread Thiago H de Paula Figueiredo
On Mon, 14 Dec 2015 09:04:15 -0200, Vangel V. Ajanovski wrote: But, this debate is fruitless, because it does not matter. I tried using "include", the problem remains. Have you tried to @Inject BeanModelSource and call