[teiid-issues] [JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter

Steven Hawkins Is the change limited only to ws translator?

What concerns me in the backport is, that class BinaryWSProcedureExecution.java is backported as a brand new class. I believe this is due to the different location of this class in upstream vs. 8.12.12.6_4.

Document/refine behavior of treating result parameter as the first parameter ---------------------------------------------------------------------------- Key: TEIID-5130 URL: https://issues.jboss.org/browse/TEIID-5130 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0, 9.3.5, 8.12.12.6_4 DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl. However in index metadata there is slightly different behavior in that the result parameter remains in it's original position. We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata.