My Oracle Support Banner

WLS 9.2 jwsc - the generated schemas have uppercase letters (Doc ID 870332.1)

Last updated on MARCH 01, 2019

Applies to:

Oracle WebLogic Server - Version 9.2 to 9.2
Information in this document applies to any platform.

Symptoms

When upgrading web services from WLS 8.1.x to WLS 9.2.x using jwsc, it is observed that many of the functions are capitialised, which causes the client code to fail, unable to find the functions.

For example, the following method

public String name;
public String getName(){return name;}
public void setName(String s){name= s;}


results in a WLS 8.1 WSDL file entry looking like this

<xs:element minOccurs='1' name='name' nillable='true' type='xs:string'/>
<xs:element minOccurs='1' name='intValue' nillable='false' type='xs:int'/>
<xs:element minOccurs='1' name='stringValue' nillable='true' type='xs:string'/>


but in WLS 9.2, the WSDL file entry is capitialised.

<xs:element minOccurs='1' name='Name' nillable='true' type='xs:string'/>
<xs:element minOccurs='1' name='IntValue' nillable='false' type='xs:int'/>
<xs:element minOccurs='1' name='StringValue' nillable='true'type='xs:string'/>


The JavaBeans properties (for example, intValue) are generated with capitialisation, whereas Section 5.4.1. of the jaxrpc-1_1-fr-spec.pdf indicates that it should be in lowercase as WLS 8.1 did.


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.