ENGAGE-106: Infusion's fluid.model.parseEL() function is broken in Kettle when Strings originated in Java code

Metadata

Source
ENGAGE-106
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Colin Clark
Created
2009-10-04T11:54:42.000-0400
Updated
2009-10-05T17:54:12.000-0400
Versions
N/A
Fixed Versions
  1. 0.1
Component
  1. Kettle

Description

parseEL() calls .toString() on the incoming EL path. In cases where the value is actually a bridged java.lang.String, toString() doesn't work. We should be explicitly coercing the value with String(EL) instead.

Comments

  • Colin Clark commented 2009-10-04T11:57:53.000-0400

    Here's a patch that fixes the issue

  • Justin Obara commented 2009-10-05T13:03:07.000-0400

    Bug Parade Engage 0.1

  • Colin Clark commented 2009-10-05T17:23:40.000-0400

    I've resolved this issue within fluid.model.parseEL() in Infusion. Needs review from Bosmon.

  • Antranig Basman commented 2009-10-05T17:54:12.000-0400

    I have reviewed this and the patch looks correct, and has not disrupted the renderer tests. It is an awkward feature of the language that it is necessary 😛