Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions messenger.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1718,12 +1718,6 @@ during a request::
}
}

.. versionadded:: 6.3

The namespace of the ``InMemoryTransport`` class changed in Symfony 6.3 from
``Symfony\Component\Messenger\Transport\InMemoryTransport`` to
``Symfony\Component\Messenger\Transport\InMemory\InMemoryTransport``.

The transport has a number of options:

``serialize`` (boolean, default: ``false``)
Expand Down Expand Up @@ -2020,12 +2014,6 @@ A single handler class can handle multiple messages. For that add the
}
}

.. deprecated:: 6.2

Implementing the :class:`Symfony\\Component\\Messenger\\Handler\\MessageSubscriberInterface`
is another way to handle multiple messages with one handler class. This
interface was deprecated in Symfony 6.2.

Binding Handlers to Different Transports
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
3 changes: 0 additions & 3 deletions messenger/multiple_buses.rst
Original file line number Diff line number Diff line change
Expand Up @@ -133,9 +133,6 @@ you can restrict each handler to a specific bus using the ``messenger.message_ha
services:
App\MessageHandler\SomeCommandHandler:
tags: [{ name: messenger.message_handler, bus: command.bus }]
# prevent handlers from being registered twice (or you can remove
# the MessageHandlerInterface that autoconfigure uses to find handlers)
autoconfigure: false

.. code-block:: xml

Expand Down