On a project, we originally used iBATIS "raw" and had the prototypical datasource defined like this:
Upon improving our application architecture to use true DAOs, we concurrently upgraded to use Spring DI in our web app and subsequently took advantage of using Spring 'template' wrappers. However, changing the configuration was quite a lesson learned on my part:
Step 1: Remove transactionManager from iBATIS
Step 2: Create new 'datasource' bean using Spring
Step 3: Create new Spring-wrapped SqlMapClient using new 'datasource' bean
I strongly encourage Java client/server/web technologies.
However, scripting languages continue to have a significant place in the market. Will Java be replaced? or will they live happily together?
Subscribe to:
Post Comments (Atom)
VisualVM on Windows with SDKMAN
7/31/2024 - I have been using SDKMAN on Windows via Git Bash for some time now and truly like it. I did however come across an interesting...
-
So... this may not be completely advisable for a production environment, but if you are using this stack, here is a snippet to show you how ...
-
Problem : On a project using iBATIS, I was receiving the following stacktrace: stacktrace org.springframework.dao.TransientDataAcces...
No comments:
Post a Comment