I exposed my service layer on server side with HttpInvoker and client can really call this layer using it's interface without knowing it is remote.
Everything works fine except I noticed that when exception is thrown on server side (service), it is propagated to remote client as it should, but with one minor difference - exception stack trace shows me method call hierarchy which led to exception on the server side, and I cannot see anywhere client side info in it, as it would be normal if remoting is not present.
How can I find out things like - which class executed this remote call? I can properly see what caused the exception inside service layer, but not where it has been called on client side.
Is it suposed to be this way ?