OpenSearch/docs/reference/migration/migrate_6_0/java.asciidoc

[[breaking_60_java_changes]]
=== Java API changes

==== `setSource` methods require XContentType

Previously the `setSource` methods and other methods that accepted byte/string representations of
an object source did not require the XContentType to be specified. The auto-detection of the content
type is no longer used, so these methods now require the XContentType as an additional argument when
providing the source in bytes or as a string.
Enforce Content-Type requirement on the rest layer and remove deprecated methods (#23146) This commit enforces the requirement of Content-Type for the REST layer and removes the deprecated methods in transport requests and their usages. While doing this, it turns out that there are many places where *Entity classes are used from the apache http client libraries and many of these usages did not specify the content type. The methods that do not specify a content type explicitly have been added to forbidden apis to prevent more of these from entering our code base. Relates #19388 2017-02-17 14:45:41 -05:00			`[[breaking_60_java_changes]]`
			`=== Java API changes`

			==== `setSource` methods require XContentType

			Previously the `setSource` methods and other methods that accepted byte/string representations of
			`an object source did not require the XContentType to be specified. The auto-detection of the content`
			`type is no longer used, so these methods now require the XContentType as an additional argument when`
			`providing the source in bytes or as a string.`