Thanks for those links, Geoff. Actually, I'm more interested in your
Grid example where you provide this component with an encoder.
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/gridwithdeletecolumn1
When I try to do likewise, my IDE complains: "Attribute t:encoder is
Thanks for those links, Geoff.
Actually, I'm more interested in your
"jumpstart/examples/tables/gridwithdeletecolumn1" Grid example where you
provide this component with an encoder. When I try to do likewise, my
IDE complains: "Attribute t:encoder is not allowed here". Not sure
whether
Hi all,
I've identified the source of the problem. It was a small omission in
the HQL which resulted in an Object[] of fields rather than an entire
entity being handed onto the Grid component, hence "[Ljava.lang.Object;"
in the exception message below.
"Could not find a coercion from
These examples might help.
read (no encoder):
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/grid
update (with encoder):
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/editablegridforupdate1
Cheers,
Geoff
> On 14 May 2022, at 7:50 am, Christopher Dodunski
You are totally right, Chris, I got you wrong. Sorry for that.
The problem may be constructor related. I remember having a similar problem a
couple of years back. In my case, if I remember correctly, it was a missing
default constructor.
Sorry this is vague. I don't have my repo available as
Thank you for those suggestions, Volker.
The common theme seems to be that I should allow Tapestry to create a
default BeanModel rather than create a new instance of one in my Java
class, correct? Your second suggestion is nearest to what I've done,
except that I return a new BeanModel.
Hi Christopher,
Here are three suggestions to achieve what you are trying to do.
(1) Omit the 'model' parameter to let Tapestry create a default model. Use the
'add' parameter to add a column named 'crewman' to that model. In the template
file, in the body of the grid component, define how to
