Theoretically yes, but the problem is, that the property is not even in the
grids bean model present. Nothing doing.
On Tue, 27 May 2014 17:40:56 +0100, Lance Java lance.j...@googlemail.com
wrote:
As a quick workaround you can use the grid's add parameter to add the
property and provide a
Exactly... And specifying an add parameter adds it to the model thus
working around the issue.
On 28 May 2014 07:35, Erich Gormann e.gorm...@gormann.de wrote:
Theoretically yes, but the problem is, that the property is not even in the
grids bean model present. Nothing doing.
On Tue, 27 May
Another solution is to override / decorate BeanModelSource. The easiest
solution is call the default implementation then add the extra
PropertyModel(s) to the BeanModel.
Thank you for the reply Lance. This was a very literal couple of lines of
javascript. The solution you posted on Git works and the T5 Initilizers
are being called as expected.
On Wed, May 21, 2014 at 3:33 AM, Lance Java lance.j...@googlemail.comwrote:
I've implemented this feature in
As your link links, you should try with Hibernate 4.3.5.Final
https://hibernate.atlassian.net/browse/HHH-8853
http://mvnrepository.com/artifact/org.hibernate/hibernate-core/4.3.5.Final
Le 28/05/14 19:14, Barry Books a écrit :
While not exactly a Tapestry Beta problem I ran into this issue
An interesting issue with the atmos library. I put the webSocket code in my
Layout component and there are no issues when I navigate about between
pages that wrap themselves in this layout. I do encounter a NullPointer
when this Layout contains another Layout and then the page. To be more
clear:
That's an unrelated but known issue.
On Wed, 28 May 2014 17:42:19 -0300, Bogdan Ivascu
ivascu.bogdan...@gmail.com wrote:
An interesting issue with the atmos library. I put the webSocket code in
my
Layout component and there are no issues when I navigate about between
pages that wrap
