I know that session bean stateful are private resource for clients, while
entity bean are mapped in DB and are shared by all users.
My need is little different:
I need a session bean modelling interaction with one client and I need
this session bean having some persistent fields. These persistent fields
must be private resource for clients because they store in a persistent
way information about session client.
So I had thought at a session bean with an entity bean as field attribte:
in such a way I think that entity bean could sure me persistence and in
the same time it is private to the client that creates the session...
is it correct?
Another approch, nearer to EJB philosophy, could be the explicit serialization
of session bean fields that store informations about client actions on DB:
what about this? Is it possible for me to explicitly "passivate" the session bean
( I don't intend to call ejbpassivate(), but getHandle() and serialize it).
Is it possible?
Do you have any idea?
thank you and bye
Domenico
===========================================================================
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".