Communication's component validator does not propagate exceptions, obscuring the cause of the error

[nikita2206]

It was quite hard to understand the issue with my request schema until I went into Magento\Framework\Communication\Config\Validator and changed exception instantiation from new LogicException($message) to new LogicException($message, 0, $e). My issue was to do with this in the end: Each getter must have a doc block. It would be better if it was possible to see that error message out of the box, but instead I was only seeing Request schema definition for topic "..." should reference existing service class. Given ... (while the class obviously existed).

Preconditions

Magento 2.2.5

Steps to reproduce

1. A schema class:

class Dummy {
    private $foo;

    public function getFoo() { return $this->foo; }
    public function setFoo($foo) { $this->foo = $foo; }
}

2. Communication configuration (communication.xml):

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Communication/etc/communication.xsd">
    <topic name="foo_topic" request="Dummy" />
</config>

3. Run validation for communication configuration. It can be done either automatically if you're using Magento EE, or can be done manually by calling into Magento\Framework\Communication\Config->getTopic("foo_topic")

Expected result

Actual result

[ArtsiomBruneuski]

#sqashtoberfest

[ArtsiomBruneuski]

#squashtoberfest

[magento-engcom-team]

@ArtsiomBruneuski thank you for joining. Please accept team invitation here and self-assign the issue.