Release Notes - 1.1
1.1.0-beta2
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 40304 | Fixes an issue where methods that are not declared in the interface are declared incorrectly as “SOAP Java Operation” objects. |
| 40055 | Fixes the wrong SOAP Java Operation Object for methods that are not declared in the Interface. |
Other Updates
| Details |
|---|
| Fix missing client-side SOAP operation requests. Improved detection of client-side calls to proxy Web Service methods. |
1.1.0-beta1
Other Updates
| Details |
|---|
| Fixed error during analysis “IndexError: list index out of range”. |
1.1.0-alpha3
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 28842 | Fixes the missing soap operations due to ‘silent’ crash coming from WSDL with no input. |
| 34861 | Deleted transactions due to missing JAX-WS SOAP operations. |
| 34615 | Deleted transactions due to missing JAX-WS SOAP operations. |
Other Updates
| Details |
|---|
| Fixed the missing SOAP operations when “message.part” WSDL node had a “type” attribute instead of an “element” attribute. |
| Added more detailed log for troubleshooting when analyzing PayloadRoot annotation. |
1.1.0-alpha2
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 27765 | Correct bug leading to disparition of SOAP Java Operations and enhancement of the algorithm for the interpretation of Spring-WS annotations. |
| 27608 | Correct difference in SOAP Java operation object number from Spring WS between snapshots for same source |
1.1.0-alpha1
Other Updates
| Details |
|---|
| Support SOAP operations handled by Jax-RPC (in EJB context) |