Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with name "Params" #94

Open
genesis-0000 opened this issue Jan 16, 2018 · 8 comments
Open

Conflict with name "Params" #94

genesis-0000 opened this issue Jan 16, 2018 · 8 comments

Comments

@genesis-0000
Copy link

I have an issue with this

xml: name "objparameters" in tag of myservice.ProcessTransaction.Objparameters conflicts with name "Params" in *myservice.Params.XMLName

What is it please?

@malaschitz
Copy link

Look into generated sources. The same tag has two different names. In myservice.ProcessTransaction.Objparameters is name "objparameters" and in myservice.Params exists "XMLName" and there is "Params". There must be bug in gowsdl. I have the same problems.

@wuryscamp
Copy link

i have the same problems

@Markvandersteen
Copy link

same here, does anyone have a fix?

@fgituser
Copy link

fgituser commented Oct 22, 2018

please fix this problem.

@zafer06
Copy link

zafer06 commented Oct 31, 2018

I have the same problem?

@colinbowern
Copy link

I think I'm running to something similar with the NetSuite SuiteTalk WSDL. I posted on StackOverflow for input on this as it is an XML encoder limitation by the looks of it, not specific gowsdl.

@colinbowern
Copy link

A suggestion I got from @mkopriva on StackOverflow:

Depending on how the un/marshaled data should look, either remove the tag or the XMLName field or edit one of those two so that they match. Here's an example (i'm not sure whether or not you need the namespace to be present so i've added it to the tag). Also note the ,chardata tag option on the Value field, without it the marshaler will add an inner element to the signature element which is not something you want I assume.

@c4milo c4milo pinned this issue Jan 7, 2019
@snowlyg
Copy link

snowlyg commented Jan 17, 2022

same here, does anyone have a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants