Originally posted by Jason Menard:
Ok, this isn't the answer you are looking for, but I feel compelled to offer my unsolicited opinion anyway. That test action... in production, it is uber-bad practice to be doing database stuff ("database stuff", that's the technical term) in your Action. *YECH* *GAG* I can honestly say that I've never used the datasource element as my webapp has never had to have access to it. Now my business objects... that's a different story. I know, I know, it's only a test. I just had to get that off my chest though as that test action just made me go into a frenzy and start breaking things in a violent rage. *Hulk Smash Puny Action Class!!!*
I now return you to your regularly scheduled topic.
I know, I know. In fact, I have even dropped the use of the
Struts defined datasource. The Struts docs even say you shouldn't use it. So I am using a
Tomcat defined datasource that works via JNDI lookup just like any other webapp I have worked on.
Thanks for you amusing opinion though.