Bug #6999
OO methods/properties used in direct Java calls
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
History
#1 Updated by Constantin Asofiei over 1 year ago
Consider this type:
using testing.PrimTest from java.
class oo.Prim:
def public property v1 as int get. set.
method public static void m1().
def var ch as char.
def var k as int.
v1 = PrimTest:testPrimitives(k, ch).
v1 = PrimTest:testPrimitives(v1, ch).
k = PrimTest:testPrimitives(k, ch).
m2(PrimTest:testPrimitives(k, ch)).
end.
method public static void m2(input i1 as int).
end.
end.
and this Java class:
package testing;
public class PrimTest
{
public static int testPrimitives(int i1, String s1)
{
System.out.println(i1 + " " + s1);
return i1;
}
}
The issue is when using a property or method with Java style calls: FWD doesn't convert properly these cases, when the Java method call is assigned to a property, the property is set as an argument to the Java method call or the Java method call is used as an argument to a 4GL call.