Thanks, not as easy as WO, but should be sufficient. Just wish there was a built in
EOF type DB layer. Going to miss that.
----Original Message-----
>From: Tim Panton <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subj: Re: Subclass session?
>Reply To: "A mailing list for discussion about Sun Microsystem's Java
Servlet API Technology." <[EMAIL PROTECTED]>
>Sent: Wednesday, March 06, 2002 5:20 AM
>
>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
>
>
___________________________________________________________________________
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
