Understanding how an extension is wired up

[former_member639706]

The Warehousing extension is being added to a B2B site. Upon adding it, On the Stock Level item the Invoice Event collection is visable on the admin tab. An ATP Formula has been set on the Base Store. The stock is now displayed on the PDP. In an OTB site I have seen an OTB instance adjust the stock levels accordingly upon completing an order, but that is not happening on the local dev instance. The question is why?

Is the impression correct that some facade within the warehousing extension is called during the order-processing process? If so, how exactly is that wired up? I don't see any relationship to the warehousing extension and any other code.

[StefanKruk]

Hello Sam Carleton,

unfortunately, I cannot answer your question directly. how the Extension is wired to the rest of hybris.

But what I can tell you is the possibilities to extend the behavior of Hybris.

In Hybris there exist multiple ways to extend the behavior. Beginning with extending and overwriting Classes and Beans. This would be the easiest method and easy to see in the Code and Setup.

Besides this, there exists the possibility to extend the behavior via Listeners and Interceptors.

Interceptors are the most common ones therefore I will not talk further about it as I believe you are already aware of how they work.

Event Listeners are a more troublesome case, as these are not directly visible because they are not directly linked.

During different Actions and Processes, different Events will be triggered. As far as I know, during the Order Processing Process different Events will be triggered as well. If the Extension is, therefore, listening for such events it is able to run additional Logic.

These are the ways a Extension can be wired to Hybris.