It's already done. When you retrieve an EJB3 proxy from JNDI, the proxy brings the InvokerLocator with it, and the Remoting client uses the parameters in the InvokerLocator. In this case, the Remoting client will use a timeout value of 3000.
I'm sorry, i haven't explained correctly.
Actually, it's indeed already done when the proxy brings the InvokerLocator from the server and the parameter is set at the server side.
But, we want to set or modify this parameter 'timeout' at the client side at every call or give a specific value for a client for example.
Ah, I see. Well, Remoting has a facility for setting the timeout for each invocation, but there's no way to access it from the EJB layer. I'm not even sure what that would look like.