I have been running unit tests through my JBuilder IDE using a DBCP datasource defined in the Spring config. At deployment time, I need the application to use a datasource bound to JNDI. My problem is that when I add the bean definition for the JNDI datasource to the Spring config, I can't run my unit tests since Spring seems to expect the datasource to be in JNDI even though it is not needed at the time.
Is there a way around this, preferrably asking Spring to ignore the fact that the Jndi datasource is not present? I will have a similar issue when moving from the EJB layer to the Web layer, as I would prefer to use the DBCP datasource there as well.
If it is not possible for Spring to ignore the missing datasource, is there a better setup I might use?
Thanks for any suggestions.