My
java experience to date is with Swing (not Spring). My application which I've been working on for some considerable time works well and I would now like to expand my system by offering the same functionality as a web based application. To cut a long story short my entire problem relates to my lack of understanding when it comes to the database handling site of the web application. My Swing application starts by reading a list of host databases from a XML file and offering a selection to the user. Easy so far - however Host 1 could be mysql, Host 2 could be Oracle etc. According to the database type the user has selected (via the Host selection) the application then loads a list of SQL statements in the specific database vendors flavour of SQL into memory where they are recalled and used throughout the application session as required. Now what is really doing my head in is how this scenario fits with database pooling and
thread safe routines, when in theory user 1 of the web application will be connected to host 1 (mysql) and user 2 may be connected to the same web application but have selected host 2 (oracle). Judging from the pile of
J2EE,
Servlet,
JSP and now Spring manuals I've been accumulating you think I would have cracked it by now, but I more confused than ever.
Help if you can - even if you tell me it can't be done so I stop wasting time and money trying to find that magic framework, architecture which is going to make a good fit.
Thanks
Dave