-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remoting server side/client side #12
Comments
This way you lose important information about exception if it happen to actually be of a valid class. E.g. if exception extends something like this: https://lib.haxe.org/p/exception/ Anyway, I'm not sure we want to fix something in hx3compat as it's supposed to be a deprecated code and users should migrate to atlernatives. |
Hej Aleksander, Thanks for your answer ! Yes I'm sure you're right about loosing some infos but this exception appeared so often to me that this is the fast way I've found to fix that for my needs. |
Don't take me wrong, I'm ok to fix things here if you can provide a reproducible sample :) |
Hej !
When an error occurs on server side, remoting often reports me "Class not found " without any class name. I get that as response : "hxrxcy0:g" which means haxe remotin, exception, class, and 0 length string so no class name.
in order to get the real exception that occurs on server side I've changed that line :
https://github.com/HaxeFoundation/hx3compat/blob/master/std/haxe/remoting/HttpConnection.hx#L108 from :
s.serializeException(e);
tos.serializeException(Std.string(e));
The text was updated successfully, but these errors were encountered: