Thanks to DwB. That helped: @Select("SELECT * FROM users") @Results({ @Result(property = "firstName", column = "first_name"), @Result(property = "lastName", column = "last_name") }) List findUsers(); ps But in case of multiple queries I need to boilerplate @Results/@Result code for each method where entity User is returned. In my case there will be a very few places so it isn't a problem, but in general I would still like to find more general solution.
1 I think you can mix xml config and annotations. Leave the @Selects in code for the actual SQL but put the part in an xml config file. The result map should be applied the object / class level (based on the namespace) so you wouldn't have to specify @Results on each method.
– AngerClown Feb 23 at 16:23.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.