My Oracle Support Banner

Unexpected Different WSDL Generations Due to JAXB Eclipselink Issue (Doc ID 1624640.1)

Last updated on SEPTEMBER 03, 2018

Applies to:

Oracle TopLink - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

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 behavior.

The expected behavior 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.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.