I'd thought of that - but was hoping for something more pervasive - we have to
use 'session' information (in particlar the user's market identifier) throughout
the application, so we must pass this around manually, rather than having it
'omnipresent'.
Interestingly, the Transactions that are created are carried in from bean to
bean transparently - I'd hoped there was something similar for this context
Thanks for the reply
Paul.
>Why can't you just save a reference to the session bean in the client? If the
>client application is brought down and you can get a session bean handle,
serialize
>it, and deserialize it when the client is brought back up.
>
>dan.
>
>Paul Nicklin wrote:
>
>> I'm currently builing a Java client application using EJBs in the server.
>> I have to store information about the currently connected user, and I can't
find
>> a useful vehicle - I thought that the session context would work, but a new
one
>> is created per 'use' of the bean. If this were an HTTP (web page/JSP etc)
then I
>> could carry this info on the HTTP Session object, is there an equivalent
object
>> that 'follows' a particular connected client?
>> What is the alternative?
>>
>> Paul.
===========================================================================
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".
