fix.
-Original Message-
From: Chris Poulsen [mailto:mailingl...@nesluop.dk]
Sent: Tuesday, June 28, 2016 16:35
To: Tapestry users
Subject: Re: Null pointer on sort with 5.3.8 that didn't occur with 5.3.7
Hook up a debugger and see what is going on when the NPE is thrown?
On Tue, Jun
nt of that column:
> >>
> >> ${ myColumn3}
> >>
> >> - In the page Java code, there is the method returning the value for
> >> that
> >> column:
> >>
> >> public String getMyColumn3()
> >> {
riginal Message-
From: Chris Poulsen [mailto:mailingl...@nesluop.dk]
Sent: Tuesday, June 28, 2016 15:32
To: Tapestry users
Subject: Re: Null pointer on sort with 5.3.8 that didn't occur with 5.3.7
Also you can control the display blocks using the data-type on the bean model,
if you need somethin
e Java code, there is the method returning the value for that
>> column:
>>
>> public String getMyColumn3()
>> {
>> return aStringThatIsNeverNull;
>> }
>>
>> So I'm trying to find out if this way of defining
; public String getMyColumn3()
> {
> return aStringThatIsNeverNull;
> }
>
> So I'm trying to find out if this way of defining my column is not right
> in 5.3.8 although it was not failing in 5.3.7, in order to rectify it.
>
>
> -
-Original Message-
From: Cezary Biernacki [mailto:cezary...@gmail.com]
Sent: Monday, June 27, 2016 18:10
To: Tapestry users
Subject: Re: Null pointer on sort with 5.3.8 that didn't occur with 5.3.7
Your stack trace seems to indicate that conduit (a mechanism connecting
Tapestry with a c
Your stack trace seems to indicate that conduit (a mechanism connecting
Tapestry with a column) is not available. It can happen if the column is
manually added to the model. Was the column sortable with Tapestry 5.3.7?
How is this column defined?
Best regards,
Cezary
On Mon, Jun 27, 2016 at 4:4
I suspect the culprit is the Java upgrade rather than Tapestry. There are
some internal changes in the sorting algorithm (for example, see
https://bugs.openjdk.java.net/browse/JDK-8062797 although it doesn't
directly match your case). But basically, you have to make sure your grid
data source doesn