You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yaroslav Molochkov (Jira)" <ji...@apache.org> on 2021/01/20 11:39:00 UTC

[jira] [Created] (IGNITE-14020) .NET: Exceptions interoperability

Yaroslav Molochkov created IGNITE-14020:
-------------------------------------------

             Summary: .NET:  Exceptions interoperability 
                 Key: IGNITE-14020
                 URL: https://issues.apache.org/jira/browse/IGNITE-14020
             Project: Ignite
          Issue Type: Improvement
          Components: platforms
    Affects Versions: 2.9.1
            Reporter: Yaroslav Molochkov


Currently it's cumbersome to make use of .net exceptions because an exception is propagated from java-side reflection or local call hence we will see lots of unrelated and, more often than not, useless frames. To avoid that the exception from the .net side needs to have registered java counterpart so we can see the exact problem clearly.

I propose to make exceptions interoperable just like types. We can resolve types between environments up to a namespace. It would be very useful to do the same with exceptions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)