When you say
"Now I wonder which way to go so as to have a few DAO methods specific
to each database server."
do you mean that you have different methods for different databases or
same methods that execute different SQL?
I was thinking that it is the latter and if so I think you can't avoid
having the configuration. It's only a matter of where the configuration
is at. Another way could be that you have the sql externalized and
inject that based on the configuration.
br,
Samuli
On 23.11.2012 10:08, Stephane-3 wrote:
Hi Samuli,
Yes, it's probably more of a Spring configuration question than a Maven one.
What I would like to avoid is having to create lots of DAO configuration
beans for nothing.
My aim is to create a DAO configuration bean and inject it only when there
is a requirement for a database server specific sql statement.
Kind Regards,
--
View this message in context:
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732594.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Remion Oy Etävalvontajärjestelmät liiketoiminnan
Samuli Saarinen tehostamiseen
gsm +358 (0)50 3560075
fax +358 (0)3 2125064 www.remion.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
