[snip]

>but that bean will need to put it somewhere stateful or discard it.  In
this
>situation you would be relying on something outside EJB to cache your data,
>unless of course that bean calls another bean that is capable of
maintaining
>conversational state.
What I think I was describing earlier was a mechanisum within EJB to store
state in an entity bean and pass that back out to the client.  All further
access
requiring this state would be managed by the entity bean.  It was an
interesting
solution to the problem

Kirk

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to