I am the first in our office to implement javabeans into a project. Normally we just access the database, store in variables and pass either in hidden fields or in the URL to the next page. Now I am having major issues and I need to know if it is the beans causing my problems.
Pages that loaded correctly are now not loading correctly. There are too many instances to go into but the pages just don't display well. Though some will if they are refreshed. If there was a problem with my code would it not display at all everytime I get the page instead of clearing up when refreshed? Or loading sometimes but not others? (and I mean with a 10 minute period).
I was demoing the project this morning, there was nothing wrong. It ran perfectly. Then all of a sudden pages that were displaying properly wouldn't display anymore. We demoed for over an hour before it crapped out. I don't think its the code because if there was a problem with it I would have gotten these errors on my machine (we were demoing on the boss' machine in another room). He thinks the problem is the javabeans.
Tomcat is giving me the error:
[Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer: socket write error
I know this isn't the sql forum but what I need to know is if javabeans can give me this error? Can they cause any errors that I might not be familiar with? Should I switch back to using request.getParameter to pass all data? I need to have a finished demo on Tuesday so I need to know fast if I need to convert all the beans over to the old request.getParameter style?