Failing test case for nested select with @Param attributes

[lkb2k]

I have modified the existing complex column test suite to add a failing test case that uses an association to a mapped statement that uses @param annotations. Other than the query being defined in the java interface and using @param instead of being in the XML the test is the same as the existing scenarios.

[emacarron]

Thanks for the detailed test.

This is indeed a bug. In 3.3.x the internal map, that holds the input parameters for a mapper, fails if a get is called for a non-existing value. This change was added to fail-fast in case that someone has used a wrong name in an XML file.

The problem is that when filling input parameters a get("firstName") is called just to see if the parameter exists and what is its type and use the proper typehandler for it. The value is not yet in the "strict" map and it fails.

We will fix this for 3.4.1.