This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new aecf717  Update camel-3-migration-guide.adoc (#3791)
aecf717 is described below

commit aecf717c568206a238506b63f6b081d849837129
Author: Matej Melko <6814482+mme...@users.noreply.github.com>
AuthorDate: Fri May 1 06:40:04 2020 +0200

    Update camel-3-migration-guide.adoc (#3791)
    
    I believe there was a typo. hasOut/getOut are methods of Exchange and those 
are now deprecated.
---
 docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc
index 23b4681..c8f217f 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc
@@ -273,9 +273,9 @@ To use this API you can get it via the `getMessage` method 
on `Exchange`:
 
 The fault API has been removed from `org.apache.camel.Message` as it was only 
used for SOAP-WS fault message. The `camel-cxf` and `camel-spring-ws` 
components for SOAP-WS has been modified to support fault messages from their 
components. The option `handleFault` has also been removed and you now need to 
turn this on as endpoint or component option on `camel-cxf` or 
`camel-spring-ws`.
 
-=== getOut on Message
+=== getOut on Exchange
 
-The `hasOut` and `getOut` methods on `Message` has been deprecated in favour 
of using `getMessage` instead. (sidenote: The camel-core are still using these 
methods in a few places to be backwards compatible and rely on this logic as 
Camel was initially designed with the concepts of IN and OUT message inspired 
from the JBI and SOAP-WS specifications).
+The `hasOut` and `getOut` methods on `Exchange` has been deprecated in favour 
of using `getMessage` instead. (sidenote: The camel-core are still using these 
methods in a few places to be backwards compatible and rely on this logic as 
Camel was initially designed with the concepts of IN and OUT message inspired 
from the JBI and SOAP-WS specifications).
 
 === OUT message removed from Simple language and Mock component
 

Reply via email to