Why uppercase properties generated within setter and getter? - lowercase required #396
Unanswered
trailsnail
asked this question in
Q&A
Replies: 1 comment
-
The getter and setter normalizes the name of the properties as get|set.ucfirst(prop) That is why you are seeing this. You can overcome this issue by creating your own get and set assembler, which has a different normalization strategy or which tries to read/write both properties. However, i. This case the real issue is the fact that both complex types get merged because they have the same name and because ext-soap is not able to do class map matching on multiple namespaces. If the case of the props in the service were consise, this wouldn't be a problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi again,
I have an WSDL file with two scheme files.
cis_bas.xsd
andbcs_base.xsd
The generated class contains lowercase properties and the same as uppercase variants.
For the uppercase variants the getter and setter are built.
This causes error since endpoint await that the lower case stuff is filled.
So how can I avoid this?
Beta Was this translation helpful? Give feedback.
All reactions