Merge branch '4.4' into 5.0

* 4.4:
  Added note regarding workflow "entered" event being dispatched on creation
  get/setThrowable

Author: OskarStark

components/http_kernel.rst

@@ -526,10 +526,22 @@ to the exception.
 
 Each listener to this event is passed a :class:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent`
 object, which you can use to access the original exception via the
-:method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getException`
+:method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getThrowable`
 method. A typical listener on this event will check for a certain type of
 exception and create an appropriate error ``Response``.
 
+.. versionadded:: 4.4
+
+    The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getThrowable` and
+    :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setThrowable` methods
+    were introduced in Symfony 4.4.
+
+.. deprecated:: 4.4
+
+    The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getException` and
+    :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setException` methods
+    are deprecated since Symfony 4.4.
+
 For example, to generate a 404 page, you might throw a special type of exception
 and then add a listener on this event that looks for this exception and
 creates and returns a 404 ``Response``. In fact, the HttpKernel component

event_dispatcher.rst

@@ -35,7 +35,7 @@ The most common way to listen to an event is to register an **event listener**::
         public function onKernelException(ExceptionEvent $event)
         {
             // You get the exception object from the received event
-            $exception = $event->getException();
+            $exception = $event->getThrowable();
             $message = sprintf(
                 'My Error says: %s with code: %s',
                 $exception->getMessage(),

reference/events.rst

@@ -239,14 +239,14 @@ sent as response::
 
     public function onKernelException(ExceptionEvent $event)
     {
-        $exception = $event->getException();
+        $exception = $event->getThrowable();
         $response = new Response();
         // setup the Response object based on the caught exception
         $event->setResponse($response);
 
         // you can alternatively set a new Exception
         // $exception = new \Exception('Some special exception');
-        // $event->setException($exception);
+        // $event->setThrowable($exception);
     }
 
 .. note::

workflow.rst

@@ -215,29 +215,29 @@ what actions are allowed on a blog post::
 
     // See all the available transitions for the post in the current state
     $transitions = $workflow->getEnabledTransitions($post);
-    
+
 Accessing the Workflow in a Class
 ---------------------------------
 
 To access workflow inside a class, use dependency injection and inject the
 registry in the constructor::
 
     use Symfony\Component\Workflow\Registry;
-    
+
     class MyClass
     {
-    
+
         private $workflowRegistry;
-    
+
         public function __construct(Registry $workflowRegistry)
         {
             $this->workflowRegistry = $workflowRegistry;
         }
-    
+
         public function toReview(BlogPost $blogPost)
         {
             $workflow = $this->workflowRegistry->get($blogPost);
-        
+
             // Update the currentState on the post
             try {
                 $workflow->apply($post, 'to_review');
@@ -339,6 +339,11 @@ order:
     The leaving and entering events are triggered even for transitions that stay
     in same place.
 
+.. versionadded:: 4.3
+
+    Following events are also dispatched when the subject enters the workflow
+    for the first time: ``workflow.entered`` and ``workflow.[worflow name].entered``.
+
 Here is an example of how to enable logging for every time a "blog_publishing"
 workflow leaves a place::