[
https://issues.apache.org/jira/browse/IGNITE-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867632#comment-15867632
]
Pavel Tupitsyn commented on IGNITE-4693:
----------------------------------------
1) Agree, fixed
2) {{ExceptionFactory}} is a delegate, not an interface. I think it is easier
for plugin authors this way (they can use anonymous methods, etc). So we can't
inject anything there. It is possible to cause another error in exception
handler in any case.
> Add possibility to wrap Java plugin exceptions to .NET plugin exceptions
> ------------------------------------------------------------------------
>
> Key: IGNITE-4693
> URL: https://issues.apache.org/jira/browse/IGNITE-4693
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
> Affects Versions: 2.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Plugins with Java part can throw custom Java exceptions, which are mapped to
> {{IgniteException}}. We should add a way for plugin authors to map their
> custom Java exceptions to corresponding .NET exceptions.
> This can be done by adding {{IPluginProvider.ConvertException}} method and
> iterating over plugins in {{ExceptionUtils.GetException}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
