Resending for due to lack of response. -Anish --
Hi, The StatefulEJBProvider in 2.2 changes the target object URI by appending "@<base64-encoded-ejb-key>". This requires that the client extract the new URI and invoke the next call on this new URI (if stateful behavior is required). I am looking for information on the rationale for doing this. For HTTP transport, shouldn't HTTPSession be used instead, to go back to the same remote ejb object? With the current approach, non-apache soap clients will not see stateful behavior. Hope I did not miss something obvious. Any help is appreciated. Thanks. -Anish --
