This is not just a missing detail in the documentation; the problem is that this method is both implemented and used inconsistently in Spring-WS itself: In the previous section we have seen that the problems with MTOM processing in Spring-WS are caused by a flaw in the design of the Spring-WS API.
There is therefore no easy fix and a proper solution will require changes to the API.
There are several known issues related to MTOM (or more generally XOP) processing in Spring-WS.
This article identifies the common root cause of these issues and discusses a possible (long term) solution.
The Spring WS client is a lightweight alternative that doesn’t need a WSDL to work.6 * You may obtain a copy of the License at 7 * 8 * 9 * 10 * Unless required by applicable law or agreed to in writing, software 11 * distributed under the License is distributed on an "AS IS" BASIS, 12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.13 * See the License for the specific language governing permissions and 14 * limitations under the License. This this 62 * will read the contents of the body directly from the stream.If you’re not familiar with generating JAXB classes, then take a look at this tutorial.Since Spring WS doesn’t use a service contract, you must know the request and response type.