If these contextual data belong to a session, then use a stateful session bean.
If they don't fit in sfsb, then save to database or ldap, etc.
If you want to stay away from sfsb, then include the context data in each invocatoin as method params, at the risk of polluting api.
Ideally we should have support for work area context propagation:
Thanks for the reply..
We dont want to pollute the APIs thats why we are looking to create a context service which should work in jboss cluster
I know JSR 149 is abandoned.
Any body knows if we can customize jboss-remoting subsystem and attach some context id in the remote EJB call in the transport itself
so that this ID can be used to fetch the context data maintained in the shared cache?