When the user opened the Expression Builder he with cursor positioned in an existing expression (other than a simple constant or column reference), the following error would be logged multiple times: java.lang.IllegalArgumentException.
This happened because FunctionForm constructor was performing a toUpper() on the category, but the UI and FunctionLibrary was using the unaltered category. It was fixed by removing the toUpper() to keep all things constent. As a result, this exception is no longer encountered.
Created attachment 957617[details]
log
When opening the expression builder with cursor positioned in an existing expression (other than a simple constant or column reference), the following error is logged multiple times:
java.lang.IllegalArgumentException: Expected argument to be non-null but got null
(relevant part of log attached)
After that, the expression builder behaves in unpredictable way (values do not update etc)
Steps to reproduce:
1. Create a new view table
2. Set the transformation SQL to SELECT concat('a', 'b') AS c1
3. Save the model
4. Place the cursor in the concat expression
5. Click the Expression Builder button
Comment 2JBoss JIRA Server
2014-11-14 19:58:05 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-2391 to Resolved
Comment 3JBoss JIRA Server
2015-02-12 08:46:45 UTC
Andrej Šmigala <asmigala> updated the status of jira TEIIDDES-2391 to Closed
Created attachment 957617 [details] log When opening the expression builder with cursor positioned in an existing expression (other than a simple constant or column reference), the following error is logged multiple times: java.lang.IllegalArgumentException: Expected argument to be non-null but got null (relevant part of log attached) After that, the expression builder behaves in unpredictable way (values do not update etc) Steps to reproduce: 1. Create a new view table 2. Set the transformation SQL to SELECT concat('a', 'b') AS c1 3. Save the model 4. Place the cursor in the concat expression 5. Click the Expression Builder button