At some point the action class has to pass data onto the JSP for displaying, such as a list of items. This data can either be placed in the session or the request, depending on how long it needs to persist. So in essence, the JSP has to work with what I view as "magical" data, since the JSP just assumes that data will be there when it needs it (checking for empty naturally to handle cases where it is not).
I was wondering if there are any best practices for dealing with the names of these variables and how to communicate which ones will exist to the JSP developer. For instance, one a page that displays the member profile, I pass the data to the request in an attribute called "profile" which I make a public constant in my action class called PROFILE_KEY. Does anyone do anything special for documentation to communicate this data transfer (like what the variable name is and what it holds and maybe how to handle it?) It just seems like a lot of effort goes into abstracting the configuration only to leave this part very fuzzy. Dan -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, <[EMAIL PROTECTED]> http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - It is not enough to succeed. Others must fail. -- Gore Vidal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
