On Nov 21, Rickard �berg quoth:
> Milan Madzia wrote:
> > Of course, I can use EntityBean. But The session bean have a lifetime
> > of client session, And session bean's are designed for this using.
>
> Note that stateful session beans really aren't designed for what you
> want.
Just a little catchup here...
Milan,
We have a web based interface to a range of business operations that we
implement as a stateless bean. The HttpSession stores our user session
(anything that would typically be part of the Stateful Session bean's
state) and we perform all the operations on the stateless bean so as to
gain the benefit of transactions and threading.
Except in a few cases, I imagine your page construction consists of
several small transactions and the entire page isn't one large
transaction. I agree that the notion of synchronizing each of your
business method calls would be cumbersome, but that's what having a
stateless session bean with required transactions alleviates. Consider
extracting out your true transactions (even if they all come down to one
or two large operations in your page) and place those in a stateless bean.
Then store your remote interface to that stateless bean in your
HttpSession.
Just my -1, 0.02USD ;-) (with apologies to marc)
C=)
--------------------------------------------------------------------------
If you want to build a ship, don't drum up people together to collect wood
and don't assign them tasks and work, but rather teach them to long for
the endless immensity of the sea. -- Antoine de Saint Exupery
--------------------------------------------------------------------------
Caskey <caskey*technocage.com> /// TechnoCage Inc.
--------------------------------------------------------------------------
It's not an optical illusion, it just looks like one. -- Phil White
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
