Hi guys,
Been trying out the new 1.1.7 release. Thanks for the DEDUP equalNULL feature. Although it's not a perfect change (I'd prefer if it was the default operation..), I guess it preserves backwards compatibility for people who are relying on ''!=''
I have found a couple of bugs that appear to have made their way into this release though
1) Can't specify the query to DB_INPUT_TABLE using the sqlQuery attribute any more. The error reported is "Can't find <SQLCode> node !".
Seems to be a typo on line 256 of DBInputTable, I think it should be
} else if (xattribs.exists(XML_SQLCODE_ELEMENT)){
otherwise the error will be thrown if there is no SQLCode attribute or child element.
2) Can't pass parameters on the command-line anymore (e.g. -P:name=value).
ComponentXMLAttributes() no longer calls the default constructor of PropertyRefResolver, which defaults to using the graphs properties, and instead passes in an empty Properties object.
Not sure what you want to do here, but need to either pass the Graph properties through the call stack, or else revert to using the default constructor if the properties parameter is null?
Regards,
Peter
Been trying out the new 1.1.7 release. Thanks for the DEDUP equalNULL feature. Although it's not a perfect change (I'd prefer if it was the default operation..), I guess it preserves backwards compatibility for people who are relying on ''!=''
I have found a couple of bugs that appear to have made their way into this release though
1) Can't specify the query to DB_INPUT_TABLE using the sqlQuery attribute any more. The error reported is "Can't find <SQLCode> node !".
Seems to be a typo on line 256 of DBInputTable, I think it should be
} else if (xattribs.exists(XML_SQLCODE_ELEMENT)){
otherwise the error will be thrown if there is no SQLCode attribute or child element.
2) Can't pass parameters on the command-line anymore (e.g. -P:name=value).
ComponentXMLAttributes() no longer calls the default constructor of PropertyRefResolver, which defaults to using the graphs properties, and instead passes in an empty Properties object.
Not sure what you want to do here, but need to either pass the Graph properties through the call stack, or else revert to using the default constructor if the properties parameter is null?
Regards,
Peter
Please sign in to leave a comment.
Comments 1