Hiya Ted Husted wrote:
>We use Spring.Web extensively, and, personally, I think it rocks! Yeah baby. >Sometime soon, I'd like to try using Spring to load the iBATIS object map directly, so >we can use a single configuration file throughout. Okay I'll bite... what does the above sentence actually mean? Are you proposing that one configure one's SqlMapper directly though Spring.NET XML - statements, result maps, etc? Spring.NET (and Spring) is a great integration technology... why would one want to subvert all the bells and whistles that one gets with the 'standard' iBatis.NET configuration files? Ok, 'subvert' is too strong a word here... I'm all for centralising configuration, but what exactly does one 'buy' by moving iBatis.NET configuration into Spring.NET? Am I just biting the wrong end of the stick here? I recently committed code to the Spring.NET CVS HEAD to facilitate the configuration of iBatis.NET SqlMappers, DaoManagers, and Daos from within Spring.NET.... nothing more than simple IFactoryObject implementations, because I felt that the configuration options offered by iBatis.NET were more than adequate. Enlighten me Ted... if you can convince me that this is a good thing, or show me how to remove the wrong end of the aforementioned stick from my mouth, please do :) Ciao Rick
