T
TT \(Tom Tempelaere\)
Hi,
I am developing the server side of an application, and I'm using session
beans. These session beans should be stateless. The functionality is
implemented with regular java classes and is in a seperate jar.
The implementation is a different context, and needs user specific data to
execute (user language, permissions, ...). The implementation is composed of
several classes, which require a database connection.
I would like to know a good strategy to pass some context object to the
implementation that provides the db connection and the user data. Can I
tweak the SessionContext object?
Thanks
I am developing the server side of an application, and I'm using session
beans. These session beans should be stateless. The functionality is
implemented with regular java classes and is in a seperate jar.
The implementation is a different context, and needs user specific data to
execute (user language, permissions, ...). The implementation is composed of
several classes, which require a database connection.
I would like to know a good strategy to pass some context object to the
implementation that provides the db connection and the user data. Can I
tweak the SessionContext object?
Thanks