Bosun (SCJP, SCWCD).
So much trouble in the world -- Bob Marley
String sessionData = "";
session.setAttribute(sessionData,data);
5.)ALL DATA needs to be kept in session because it may be used in future
String sessionData = "";
session.setAttribute(sessionData,data);
code:
--------------------------------------------------------------------------------
session.setAttribute( "thisIsTheNameOfTheVariable", variableData );
--------------------------------------------------------------------------------
Originally posted by Will Sillmon Jr.:
So is there a need for me to declare "thisIsTheNameOfTheVariable" or does this statement do it for me. I guess that's what I was trying to do in the previous code that I provided.
Originally posted by Will Sillmon Jr.:
Is there a way to seperate what fields should be kept as request scope and which should be applied to the session. The only reason why I am using session scope is because there will be a login screen that must be completed before you are able to access this screen. Should I just keep the items on that screen session scope and make these fields request?
Originally posted by Will Sillmon Jr.:
2.) servlet: takes company and key and runs query on them and retuns a 180 char string called myResponse.
3.)myResponse: subString is used to divide string into different fields and each field is then given a name.
Ever Existing, Ever Conscious, Ever-new Bliss
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |