[
https://issues.apache.org/jira/browse/IGNITE-28039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062627#comment-18062627
]
Ignite TC Bot commented on IGNITE-28039:
----------------------------------------
{panel:title=Branch: [pull/12844/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12844/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8907631&buildTypeId=IgniteTests24Java8_RunAll]
> Remove dependency on BinaryObjectException in MetadataRemoveProposedMessage
> ---------------------------------------------------------------------------
>
> Key: IGNITE-28039
> URL: https://issues.apache.org/jira/browse/IGNITE-28039
> Project: Ignite
> Issue Type: Improvement
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Minor
> Labels: IEP-132
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{MetadataRemoveProposedMessage#rejectionError}} method should return a
> {{{}String{}}}, and the conversion of this string into a
> {{BinaryObjectException}} should be handled by {{{}MetadataUpdateResult{}}},
> where this method is only called.
> This will make the message even closer to a POJO, and
> {{BinaryObjectException}} can be removed from the imports: the message class
> does not need to know about this exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
