More doc updates for 2.0.0

Author: robertlazarski

src/site/markdown/release-notes/2.0.0.md

@@ -6,10 +6,16 @@ and Wildfly 32, and is expected to support EE 10 and Spring 6 / Spring Boot 3.
 
 The Axis2 project transition to jakarta depends partly on Axiom, which has also been updated to 2.0.0.
 
-Axis2 added two committers recently and after this big jakarta update that changed nearly every file and dependency of the project, the community can once again expect releases several times a year to fix bugs and update dependencies with CVE's.
+HTTPClient has been updated to 5.x, so update your axis2.xml files from httpclient4 to httpclient5. 
+
+Previously generated sources with javax references may or may not work in the latest Tomcat / Wildfly. You may have to regenerate your sources or globably replace the jakarta libs.  
 
 The JSON support has been updated with many bugs fixed, while the examples have
-been updated to use Spring Boot 3. Axis2 isn't just for SOAP anymore, as some committers currently only use JSON in their own projects and not SOAP at all.
+been updated to use Spring Boot 3. If you want to support native JSON with simple POJO's and no SOAP, axis2 can that. See the new enableJSONOnly flag in axis2.xml. 
+
+For those who want to support both SOAP and JSON, the JSON support docs for the XML Stream API Base Approach have been improved.
+
+Axis2 added two committers recently and after this big jakarta update that changed nearly every file and dependency of the project, the community can once again expect releases several times a year to fix bugs and update dependencies with CVE's.
 
 The main purpose of the release is to upgrade everything possible to the latest,
 and have our Jira issues cleaned up. Many issues have been fixed. 
@@ -37,6 +43,8 @@ For those interested in Rampart - an optional implementation of WS-Sec* standard
 
 Apache Axis2 2.0.0 Jira issues fixed
 ------------------------------------
+
+        Release Notes - Axis2 - Version 2.0.0
                 
 <h2>        Bug
 </h2>
@@ -51,8 +59,6 @@ Apache Axis2 2.0.0 Jira issues fixed
 </li>
 <li>[<a href='https://issues.apache.org/jira/browse/AXIS2-5964'>AXIS2-5964</a>] -         AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
 </li>
-<li>[<a href='https://issues.apache.org/jira/browse/AXIS2-5971'>AXIS2-5971</a>] -         AxisServlet.processURLRequest use content-type header instead of accept
-</li>
 <li>[<a href='https://issues.apache.org/jira/browse/AXIS2-6030'>AXIS2-6030</a>] -         Axis2 connections are not returned to connection pool on 1.8.0 with JAXWS
 </li>
 <li>[<a href='https://issues.apache.org/jira/browse/AXIS2-6035'>AXIS2-6035</a>] -         Axis2 libraries not compatible with Tomcat 10
@@ -93,6 +99,8 @@ Apache Axis2 2.0.0 Jira issues fixed
 </li>
 <li>[<a href='https://issues.apache.org/jira/browse/AXIS2-6075'>AXIS2-6075</a>] -         axis2-wsdl2code-maven-plugin documentation is stuck on version 1.7.9
 </li>
+<li>[<a href='https://issues.apache.org/jira/browse/AXIS2-6080'>AXIS2-6080</a>] -         Axis2 1.8.2 Missing Libraries for Apache Tomcat 11.0.2
+</li>
 </ul>
                 
 <h2>        Improvement

src/site/xdoc/docs/json_support_gson.xml

@@ -31,7 +31,9 @@
 	   similar in features though Moshi is widely considered to have better
 	   performance. GSON development has largely ceased. Switching between
 	   Moshi and GSON is a matter of editing the axis2.xml file. 
-	   For users of JSON and Spring Boot, see the sample application in 
+	</p>
+	<p>
+	   For users of JSON and Spring Boot, the Native approach discussed below can be seen as a complete sample application in 
 	   the <a href="json-springboot-userguide.html">JSON and Spring Boot 3 User's Guide.</a> 
 	</p>
         <p>This documentation explains how the existing JSON support in Apache Axis2 have been improved with two new
@@ -172,7 +174,7 @@
                 the XmlSchema it can provide accurate XML infoset of the JSON message. To get the relevant XMLSchema
                 for the operation, it uses element qname of the message. At the MessageBuilder level Axis2 doesn't know
                 the element qname hence it can't get the XmlSchema of the operation. To solve this issue Axis2 uses a
-                new handler call JSONMessageHandler, which executes after the RequestURIOperationDispatcher handler.
+                new handler call JSONMessageHandler, which executes after the RequestURIOperationDispatcher handler or optionally the JSONBasedDefaultDispatcher that can be used in the native approach though it is not mandatory (See the JSON based Spring Boot User Guide). 
                 In the MessageBuilder it creates GsonXMLStreamReader parsing JsonReader instance which is created using
                 inputStream and stores it in input MessageContext as a message property and returns a default SOAP
                 envelop. Inside the JSONMessageHandler it checks for this GsonXMLStreamReader property, if it is not