Unexpected Different WSDL Generations Due to JAXB Eclipselink Issue
Last updated on AUGUST 16, 2016
Applies to:Oracle TopLink - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
A WebService application is deployed into 12.1.2 WebLogic server (WLS) .
A web service can be invoked through sayHello method which :
- has Input parameter input (examples.jaxws2.Input;)
- returns as Output (examples.jaxws3.Output;)
This is an unexpected behaviour .
The expected behaviour is that once the WebService is deployed , the corresponding WSDL from WebLogic is the same .
The issue is related to the implementation of JAXB (MoxyEclipseLInk ) as if switching to the JAXB GlassFish RI implementation, the obtained WSDL is always the same.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms