Open fancellu opened 9 years ago
Well, I found a way around this, just use a plain Vaadin Table. Not exactly ideal, but does show that what I'm trying to do isn't unreasonable.
If this could be fixed it would be really nice, currently by code is littered with Java level hacks.
Thanks.
So the problem is that your are using the Vaadin SQLContainer because there is no a Scaladin wrapper for the SQLContainer?
Yep. In the main it works fine, but as I said, in certain circumstances will go bang with a match error
+1 please
getItem fails on a Table with a SQLContainer as data source.
Looks v similar to #24
I have a Table and I set the data source via
p.setContainerDataSource(usersContainer)
usersContainer is an SQLContainer.
Now all is fine, can make it editable, save to DB. But, I now need to change one of the cells to a combo, so I try setting tableFieldFactory, but on editable=true I get a big stack trace
If I don't go editable OR don't mess with tableFieldFactory, its fine, but I need to do both.
In fact I do both elsewhere in my app, but container is standard inmemory IndexedContainer, and not SQLContainer.
Any idea of a way around this?
Thanks.