Bug #2450
merging the name_map_merge.xml into the main name_map.xml ignores program arguments and internal entries
Start date:
11/25/2014
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Constantin Asofiei over 9 years ago
- File ca_upd20141125a.zip added
- Status changed from WIP to Review
Attached update solves a problem related to specifying program arguments/internal entries in the name_map_merge.xml file. Now constructs like this are possible and merged properly:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <name-map> <class-mapping jname="foo.SomeProgram" pname="foo/some-program.p"> <parameter buffer="some-table" for="some-table" type="BUFFER"/> <parameter jname="arg1" mode="INPUT" pname="arg1" type="CHARACTER"/> <method-mapping jname="someMethod" pname="some-method" returns="CHARACTER" type="FUNCTION"> <parameter jname="farg1" mode="INPUT" pname="farg1" type="CHARACTER"/> </method-mapping> </class-mapping> </name-map>
#2 Updated by Greg Shah over 9 years ago
Code Review ca_upd20141125a.zip
I'm fine with the changes.
If this passed conversion regression testing, then please check it in.
#3 Updated by Constantin Asofiei over 9 years ago
Greg Shah wrote:
If this passed conversion regression testing, then please check it in.
Testing passed, released to bzr rev 10665.
#4 Updated by Greg Shah over 9 years ago
- Status changed from Review to Closed