RE: Frames, concurrency, and EJB Stateful Session beans - a probl em.

Yup, that's where I would put the synchronization.  At first guess I would think this would be simpler than the general purpose approach, because you've placed all responsibility for synchronization in a distinct spot - the xxxHandler.  Any user of the handler doesn't have to even think abou

RE: Frames, concurrency, and EJB Stateful Session beans - a probl em.

eans, and use a business interface for them as well. No real thoughts on entity bean handlers, though.) --jason -Original Message- From: Deadman, Hal [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 12:00 PM To: [EMAIL PROTECTED] Subject: RE: Frames, concurrency, and EJB Stateful Se

Re: Frames, concurrency, and EJB Stateful Session beans - a probl em.

So in your scenario (as a proposed solution to my problem), I would add syncronization code to xxxHandler.java? That seems elegant; I had never thought of implementing a separate handler class for my EJB's, although it's always been on my "to-do" list to try having Bean and Remote implement a comm

RE: Frames, concurrency, and EJB Stateful Session beans - a probl em.

re state (cookies, session, db). I would be interested to hear when people have found them to be useful. Hal > -Original Message- > From: Jason Pringle [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 05, 2001 2:41 PM > To: '[EMAIL PROTECTED]' > Subject: RE: Fram