what we generally do is to create a single bean per concept (eg a logged in user) the bean extends Object and implements SessionBindingListener and Serializable. The bean has properties that hold all the relevant details. At session creation we put an instance of this bean into the session, with a suitable key (eg "logged in user"). Subsequent pages then have to: get the session get the bean cast the bean use the accessors on the bean In short the session 'has a' bean. In WO it 'is a' bean.
URL http://www.westpoint.ltd.uk/ - internet recon. ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
