| 
|
| 
|
Java serialization requests
Overview
Java Serialization on top of the HTTP protocol allows remote service calls to be executed between the client and server using specific Frameworks such as Spring Remoting (Spring HTTP Invoker). The data exchange is carried out in binary and encapsulated in the HTTP protocol.
The Java Serialization module allows load testing web applications programmed in Java and using specific Frameworks such as Spring Remoting (Spring HTTP Invoker).
To be able to handle Java Serialization requests, you will need to purchase the optional Java Serialization module. This module is included in the demo version of NeoLoad.
- Warning: RMI over HTTP is not supported.
Dependent libraries
When recording Java Serialization requests, you will need to load the Java classes for the objects exchanged, as well as the client interfaces for the called services. See Java Serialization.
Recording
The following diagram shows how the Java Serialization module works during recording:
The binary data exchanged between the client and server passes through the recording proxy. The Java Serialization module comes into play as the data travels through the proxy, analyzing and decoding the requests. Once translated into XML, the requests are inserted in the project.
- Warning: Only requests with the Content-Type: application/x-java-serialized-object header are recorded.
Runtime
The following diagram shows how the Java Serialization module works during a test run:
The XML request variables are evaluated and the module engine translates the XML to binary data. This data is then sent to the server. The binary response received is translated into XML, after which the validity checks and Variable Extractors in the played request are executed.