Correct!
it was code within the UserAccountManager.getUserAccountDetails() method!
I didn't print the entire class bcause it's quite big and didn't want to clog the post with lines and lines of code. i presumed it was OK because it was working (the idea of passing the results to a Bean was the new bit) so I presumed that was causing the problem, but it wasn't!
Cheers anyway for confirmation that what I was doing was correct (well would work) meant I started looking inside the getUserAccountDetails method instead.
On a similar note, is it 'good practice' to use this style (retuning SQL results to a Bean)?
I ask because I have done the similar thing with another SQL query, but one that will return multiple results.
I then put each one into a Vector
e.g
So basically I'm creating a Vector of Beans each Bean for a row of results found, then passing the Vector back which is then being stored in something like 'request.setAttribute("result", vector)' so that a
JSP can recall the results from the Vector.
My only concern is memory issues. Say the query returns a 1,000 (possibly more) items. That's 1,000 beans stored in a Vector passed to the JSP!
Could there be problems with memory/performace?
Obviously you don't know the H/W specs of the server being used (neither do I t this time!!!) but is this a bad style to use?
Just wondering about opinion really.
Cheers