You can delay parameterClass to runtime already - you don't need to specify
it at configuration time.
For results, you could use a HashMap as the resultclass and then convert to
your desired class, or you could specify some common interface and use the
ResultObjectFactory to specify the implementation at runtime.
Lastly, if this has something to do with polymorphic queries, then you might
take a look at the <discriminator> tag - it might do what you want.
Jeff Butler
On 1/30/07, Abdullah Kauchali <[EMAIL PROTECTED]> wrote:
... instead of in the sqlmap xml files?
Given this hypothetical sqlmap (without explicit parameterClass and
resultClass):
<select id="selectAllPersons">
SELECT [person_id] id
,[person_name] name
,[person_description] description
FROM [TBL_person]
</select>
What do you guys think of the opportunity to delay the choice of
specifying
resultClass or parameterClass at the point of call:
queryForList("selectAllPersons", com.MyParameterClass.class,
com.MyResultClass.class);
... as long as the beans (either one of them) support the
methods/properties?
Is that even possible?
Comments?
